Configuración y estructura de un proyecto Phoenix

Hello! In this lesson, we'll begin our journey with Phoenix, Elixir's powerful web framework. Phoenix helps you build robust, high-performance web applications and APIs.

It leverages the speed and fault-tolerance of the Erlang Virtual Machine (BEAM) through Elixir, making it ideal for real-time features and concurrent systems.

Phoenix combines the elegance of Elixir with the reliability of Erlang/OTP. This means your applications can handle many concurrent users with low latency and are highly resilient to failures.

It's a fantastic choice for building anything from simple websites to complex real-time applications like chat rooms or live dashboards.

Before we create a Phoenix project, ensure you have Elixir and Erlang installed on your system. You can check your versions using the commands below.

If you don't have them, consider using asdf for easy installation and version management.

The easiest way to start a new Phoenix project is by using the mix phx.new command. This command sets up a new application with all the necessary files and dependencies.

Let's create our first project, named hello_phoenix:

After running mix phx.new hello_phoenix, a new directory named hello_phoenix is created. Inside, you'll find a well-organized set of folders and files.

This structure helps keep your code modular and maintainable as your application grows.

Let's look at some of the top-level directories:

• assets/: Contains your frontend files like CSS, JavaScript, and images.
• config/: Holds configuration files for different environments (development, test, production).
• priv/: Stores private application resources, such as database migrations and static files not served directly.

The lib/ directory is the heart of your Elixir application. For Phoenix projects, it usually contains two main sub-directories:

• lib/hello_phoenix/: Your core application logic and business rules.
• lib/hello_phoenix_web/: Web-specific components like controllers, views, and routers.

This separation helps keep your web interface distinct from your core logic.

Inside lib/hello_phoenix_web/, you'll find router.ex. The router is like the traffic cop of your web application.

It defines how incoming web requests (like visiting a URL) are mapped to specific actions within your application, typically handled by controllers.

After generating your project and installing dependencies (mix deps.get), you can start the development server. This compiles your code and makes your application accessible in your browser, usually at localhost:4000.

Navigate into your project directory first!

The mix phx.new command creates a standard Phoenix project. Which directory is typically used for frontend assets like CSS and JavaScript?

Great job! You've successfully created your first Phoenix project using mix phx.new. We explored the basic directory structure, including assets/, config/, lib/, and priv/.

You now have an understanding of where your core application logic lives (lib/hello_phoenix) and where web-specific components reside (lib/hello_phoenix_web), including the crucial router.ex. Next, we'll dive deeper into how routing works and how controllers handle requests!