Added SQLite changes in Docker article for v14 and v16

14/umbraco-cms/fundamentals/setup/install/running-umbraco-on-docker-locally.md

@@ -1,74 +1,141 @@
 ---
-description: "Running Umbraco on docker locally using docker compose"
+description: Running Umbraco on docker locally using docker compose
 ---
 
 # Running Umbraco in Docker using Docker Compose
 
-To aid in developing Umbraco with additional services, the templates can provide the requisite files to run Umbraco with an SQL Server database in Docker. This setup is designed to be used for local development, and not for production.
+This article shows how to run Umbraco locally in Docker using Docker Compose. You can use either SQL Server or SQLite for development.
+
+{% hint style="info" %}
+This setup is intended for local development only. It is not recommended for production environments.
+{% endhint %}
 
 ## Prerequisites
 
-Before you can run Umbraco in Docker, you need to have the following installed:
-* Version 14.3.0 or higher of the Umbraco Templates
+Before you can run Umbraco in Docker, make sure the following are installed:
+
+* .NET SDK with Umbraco Templates v14.3.0 or higher
 * Docker Desktop
 
 ## Installing
 
-Installing Umbraco with the Docker file and Docker Compose file is a two-step process.
+To install Umbraco using the provided Dockerfile and Docker Compose setup, follow these steps:
+
+### Option 1: Using SQL Server
 
-1. Create a folder to hold your project and enter that folder.
+1. Create a folder and navigate into it:
 
 ```bash
 mkdir MyDockerProject
 cd MyDockerProject
 ```
-2. Create your Umbraco project using the Umbraco Templates, and remember to use the `--add-docker` flag to include the Docker files.
 
+2. Create a new Umbraco project with Docker support:
 
-Conventionally this is named the same as the folder, but it is not a requirement.
-
-```bash
+```csharp
 dotnet new umbraco -n MyDockerProject --add-docker
 ```
 
-Now we need to add some additional files to make docker compose work. We can do this using the umbraco-compose template, passing the project name we specified earlier to the -P parameter:
+3. Add Docker Compose files:
 
-```bash
+```csharp
 dotnet new umbraco-compose -P "MyDockerProject"
 ```
 
-The `-P` flag is required to specify the correct paths in the docker-compose file. The project is now ready to run with docker compose.
+The `-P` flag is required to specify the correct paths in the docker-compose file. The project is now ready to run with Docker Compose.
 
-The final folder structure looks like this:
+The folder structure should now look like this:
 
-* MyDockerProject
-  * MyDockerProject
-    * Typical project files
-    * DockerFile
-    * `.dockerignore`
-  * `.env`
-  * Database
-    * DockerFile
-    * `healthcheck.sh`
-    * `setup.sql`
-    * `startup.sh`
-  * `docker-compose.yml`
+* MyDockerProject/
+  * Database/
+    * Dockerfile
+    * healthcheck.sh
+    * setup.sql
+    * startup.sh
+  * MyDockerProject/
+    * Your project files
+    * Dockerfile
+    * .dockerignore
+  * .env
+  * docker-compose.yml
 
 The project now includes docker files for both Umbraco and the SQL server database.
 
 It also includes additional scripts to launch and configure the database and a `.env` file with the database password.
 
-## Running
+4. Run the following command from the root folder (where `docker-compose.yml` is located):
+
+```bash
+docker compose up
+```
+
+5. Access the site at `http://localhost:44372`.
+
+### Option 2: Using SQLite
+
+1. Create a new folder and navigate into it:
+
+```bash
+mkdir MyDockerSqliteProject
+cd MyDockerSqliteProject
+```
+
+2. Create a new Umbraco project:
+
+```csharp
+dotnet new umbraco -n MyDockerSqliteProject
+```
+
+3. Add a Dockerfile
+
+{% code overflow="wrap" fullWidth="false" %}
+```bash
+FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base
+WORKDIR /app
+EXPOSE 8080
+
+FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build
+ARG BUILD_CONFIGURATION=Release
+WORKDIR /src
+COPY ["MyDockerSqliteProject/MyDockerSqliteProject.csproj", "MyDockerSqliteProject/"]
+RUN dotnet restore "MyDockerSqliteProject/MyDockerSqliteProject.csproj"
+COPY . .
+WORKDIR "/src/MyDockerSqliteProject"
+RUN dotnet build "MyDockerSqliteProject.csproj" -c  $BUILD_CONFIGURATION -o /app/build
+
+FROM build AS publish
+RUN dotnet publish "MyDockerSqliteProject.csproj" -c  $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false
+
+FROM base AS final
+WORKDIR /app
+COPY --from=publish /app/publish .
+ENTRYPOINT ["dotnet", "MyDockerSqliteProject.dll"]
+```
+{% endcode %}
+
+{% hint style="info" %}
+To speed up the build process, add a `.dockerignore` file to exclude unnecessary folders like `.git`, `bin`, and `obj`.
+{% endhint %}
+
+4. Build the container:
+
+```bash
+docker build -t umbraco-sqlite .
+```
+
+5. Run the container:
 
-To run the project use the `docker compose up` command in the root of the project files where the `docker-compose.yml` is.
+```bash
+docker run -p 8080:8080 umbraco-sqlite
+```
 
-This command will build both the Umbraco and SQL Server images and launch them in the correct order. When the site is booted, access it in your browser on `http://localhost:44372/`.
+6. Access the site at `http://localhost:8080`.
 
-### Useful commands
+## Useful Commands
 
 There are some useful commands you can use to manage the docker containers:
 
-* `docker compose down --volumes`: Delete your containers and the volumes they use. This is useful if you want to start from scratch.
+* `docker compose down --volumes`: Deletes containers and the volumes they use. This is useful if you want to start from scratch.
 
 {% hint style="warning" %}
 Be careful with this command, as it deletes your database and all data in it.
@@ -77,7 +144,7 @@
 * `docker compose up --build`: Rebuild the images and start the containers. This is useful if you have made changes to the project and want to see them reflected on the running site.
 * `docker compose watch`: Start the containers and watch the default models folder. This means that if the project uses a source-code models builder the images are automatically rebuilt and restarts when you change the models.
 
-## Details
+## Bind Mounts (SQL Server setup)
 
 The docker compose file uses bind mounts for the following folders:
 
@@ -91,10 +158,10 @@
 
 For local development, however, this means that the files necessary for development are available from outside the container in your IDE. This allows development even though the project is running in docker.
 
-## Template options
+## Template Options (SQL Server only)
 
-The `umbraco-compose` template has a few options that can be used to customize the setup:
+The `umbraco-compose` template supports:
 
 * `-P` or `--project-name`: The name of the project. This is required and used to set the correct paths in the docker-compose file.
-* `-dbpw` or `--DatabasePasswor`: Used to specify the database password. This is stored in the `.env` file and defaults to: `Password1234`.
+* `-dbpw` or `--DatabasePassword`: Used to specify the database password. This is stored in the `.env` file and defaults to: `Password1234`.
 * `-p` or `--Port`: Used to specify the port the site will run on. Defaults to `44372`.

16/umbraco-cms/fundamentals/setup/install/running-umbraco-on-docker-locally.md

@@ -1,74 +1,141 @@
 ---
-description: "Running Umbraco on docker locally using docker compose"
+description: Running Umbraco on docker locally using docker compose
 ---
 
 # Running Umbraco in Docker using Docker Compose
 
-To aid in developing Umbraco with additional services, the templates can provide the requisite files to run Umbraco with an SQL Server database in Docker. This setup is designed to be used for local development, and not for production.
+This article shows how to run Umbraco locally in Docker using Docker Compose. You can use either SQL Server or SQLite for development.
+
+{% hint style="info" %}
+This setup is intended for local development only. It is not recommended for production environments.
+{% endhint %}
 
 ## Prerequisites
 
-Before you can run Umbraco in Docker, you need to have the following installed:
-* Version 14.3.0 or higher of the Umbraco Templates
+Before you can run Umbraco in Docker, make sure the following are installed:
+
+* .NET SDK with Umbraco Templates v16 or higher
 * Docker Desktop
 
 ## Installing
 
-Installing Umbraco with the Docker file and Docker Compose file is a two-step process.
+To install Umbraco using the provided Dockerfile and Docker Compose setup, follow these steps:
+
+### Option 1: Using SQL Server
 
-1. Create a folder to hold your project and enter that folder.
+1. Create a folder and navigate into it:
 
 ```bash
 mkdir MyDockerProject
 cd MyDockerProject
 ```
-2. Create your Umbraco project using the Umbraco Templates, and remember to use the `--add-docker` flag to include the Docker files.
 
+2. Create a new Umbraco project with Docker support:
 
-Conventionally this is named the same as the folder, but it is not a requirement.
-
-```bash
+```csharp
 dotnet new umbraco -n MyDockerProject --add-docker
 ```
 
-Now we need to add some additional files to make docker compose work. We can do this using the umbraco-compose template, passing the project name we specified earlier to the -P parameter:
+3. Add Docker Compose files:
 
-```bash
+```csharp
 dotnet new umbraco-compose -P "MyDockerProject"
 ```
 
-The `-P` flag is required to specify the correct paths in the docker-compose file. The project is now ready to run with docker compose.
+The `-P` flag is required to specify the correct paths in the docker-compose file. The project is now ready to run with Docker Compose.
 
-The final folder structure looks like this:
+The folder structure should now look like this:
 
-* MyDockerProject
-  * MyDockerProject
-    * Typical project files
-    * DockerFile
-    * `.dockerignore`
-  * `.env`
-  * Database
-    * DockerFile
-    * `healthcheck.sh`
-    * `setup.sql`
-    * `startup.sh`
-  * `docker-compose.yml`
+* MyDockerProject/
+  * Database/
+    * Dockerfile
+    * healthcheck.sh
+    * setup.sql
+    * startup.sh
+  * MyDockerProject/
+    * Your project files
+    * Dockerfile
+    * .dockerignore
+  * .env
+  * docker-compose.yml
 
 The project now includes docker files for both Umbraco and the SQL server database.
 
 It also includes additional scripts to launch and configure the database and a `.env` file with the database password.
 
-## Running
+4. Run the following command from the root folder (where `docker-compose.yml` is located):
+
+```bash
+docker compose up
+```
+
+5. Access the site at `http://localhost:44372`.
+
+### Option 2: Using SQLite
+
+1. Create a new folder and navigate into it:
+
+```bash
+mkdir MyDockerSqliteProject
+cd MyDockerSqliteProject
+```
+
+2. Create a new Umbraco project:
+
+```csharp
+dotnet new umbraco -n MyDockerSqliteProject
+```
+
+3. Add a Dockerfile
+
+{% code overflow="wrap" fullWidth="false" %}
+```bash
+FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base
+WORKDIR /app
+EXPOSE 8080
+
+FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build
+ARG BUILD_CONFIGURATION=Release
+WORKDIR /src
+COPY ["MyDockerSqliteProject/MyDockerSqliteProject.csproj", "MyDockerSqliteProject/"]
+RUN dotnet restore "MyDockerSqliteProject/MyDockerSqliteProject.csproj"
+COPY . .
+WORKDIR "/src/MyDockerSqliteProject"
+RUN dotnet build "MyDockerSqliteProject.csproj" -c  $BUILD_CONFIGURATION -o /app/build
+
+FROM build AS publish
+RUN dotnet publish "MyDockerSqliteProject.csproj" -c  $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false
+
+FROM base AS final
+WORKDIR /app
+COPY --from=publish /app/publish .
+ENTRYPOINT ["dotnet", "MyDockerSqliteProject.dll"]
+```
+{% endcode %}
+
+{% hint style="info" %}
+To speed up the build process, add a `.dockerignore` file to exclude unnecessary folders like `.git`, `bin`, and `obj`.
+{% endhint %}
+
+4. Build the container:
+
+```bash
+docker build -t umbraco-sqlite .
+```
+
+5. Run the container:
 
-To run the project use the `docker compose up` command in the root of the project files where the `docker-compose.yml` is.
+```bash
+docker run -p 8080:8080 umbraco-sqlite
+```
 
-This command will build both the Umbraco and SQL Server images and launch them in the correct order. When the site is booted, access it in your browser on `http://localhost:44372/`.
+6. Access the site at `http://localhost:8080`.
 
-### Useful commands
+## Useful Commands
 
 There are some useful commands you can use to manage the docker containers:
 
-* `docker compose down --volumes`: Delete your containers and the volumes they use. This is useful if you want to start from scratch.
+* `docker compose down --volumes`: Deletes containers and the volumes they use. This is useful if you want to start from scratch.
 
 {% hint style="warning" %}
 Be careful with this command, as it deletes your database and all data in it.
@@ -77,7 +144,7 @@
 * `docker compose up --build`: Rebuild the images and start the containers. This is useful if you have made changes to the project and want to see them reflected on the running site.
 * `docker compose watch`: Start the containers and watch the default models folder. This means that if the project uses a source-code models builder the images are automatically rebuilt and restarts when you change the models.
 
-## Details
+## Bind Mounts (SQL Server setup)
 
 The docker compose file uses bind mounts for the following folders:
 
@@ -91,9 +158,9 @@
 
 For local development, however, this means that the files necessary for development are available from outside the container in your IDE. This allows development even though the project is running in docker.
 
-## Template options
+## Template Options (SQL Server only)
 
-The `umbraco-compose` template has a few options that can be used to customize the setup:
+The `umbraco-compose` template supports:
 
 * `-P` or `--project-name`: The name of the project. This is required and used to set the correct paths in the docker-compose file.
 * `-dbpw` or `--DatabasePassword`: Used to specify the database password. This is stored in the `.env` file and defaults to: `Password1234`.