use custom HTTP public port to use rootless containers by default

This commit introduces two new global constants MY_PUBLIC_URL and
IMG_PUBLIC_URL which should be used now to build URLs.

For alpha and production Ruby environments, they are fixed with their real
values directly in the `config/environments/*.rb` files.

For the development Ruby environment, they are defined by default to
`http://dlfp.lo` and `http://image.dlfp.lo`. You can customize either by
updating the `config/environments/development.rb` file or by setting the
*process* environment variables `DOMAIN`, `DOMAIN_HTTP_PORT`, `IMAGE_DOMAIN`
and `IMAGE_DOMAIN_HTTP_PORT`.

For containers, you can set these variables in the `deployment/default.env`
file.

Author: Trim

Container.md

@@ -5,60 +5,53 @@ To simplify set up of a development environment, LinuxFr.org can be
 run with a container engine like Docker or Podman with the [`compose.yml`](./compose.yaml)
 file which describes how to build all needed services.
 
-If you use the Docker engine, you can use the `docker compose up` command to start the system (you
-need to install the [Docker compose plugin](https://docs.docker.com/compose/)).
+By default, the LinuxFr.org services will be provided under the domain names
+`dlfp.lo` and `image.dlfp.lo`. So you'll need to add the
+following line into the `/etc/hosts` file of your machine:
+
+  ```
+  127.0.0.1 dlfp.lo image.dlfp.lo
+  ```
+
+Then, if you use the Docker engine, you can use the `docker compose up`
+command to start the system (you need to install the
+[Docker compose plugin](https://docs.docker.com/compose/) first).
 
 > Note: with the Docker engine, you need to enable the Docker BuildKit builder.
 > Either you have a Docker version which uses it by default, or you set the
 > environment variable `export DOCKER_BUILDKIT=1`.
 
-If you use Podman, you can either use the same Docker compose plugin or the
-[podman-compose](https://github.com/containers/podman-compose/)
-utility. The podman cli itself provide a wrapper of one of these two tools through the
+If you use the Podman engine, you can either use the same Docker compose plugin
+or the [podman-compose](https://github.com/containers/podman-compose/)
+tool. The podman cli itself provides a wrapper of one of these two tools
+through the
 [`podman compose` command](https://docs.podman.io/en/latest/markdown/podman-compose.1.html).
 Thus you need to use the `podman compose up` command to start the system.
 
-At this point, the documentation will give you `docker compose` commands, but you should be able
-to use `podman compose` without any issue.
+At this point, this documentation will give you `docker compose` commands,
+but you should be able to use `podman compose` without any issue.
 
-To init the SQL database schema, you need to wait up to the `database`
-container to be ready to listen MySQL connections.
+To setup the SQL database schema, you need to wait until the `database`
+container becomes ready to listen MySQL connections.
 
 For example, you should see in the logs:
 
-> database_1       | 2020-09-21 16:03:12 139820938893312 [Note] mysqld: ready for connections.
+> database_1       | 2020-09-21 16:03:12 139820938893312 [Note] *mysqld: ready for connections.*
 >
 > database_1       | Version: '10.1.46-MariaDB-1\~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
 
-Or you can check the `database` container status to be "healthy".
+Or you can check the `database` container status to be *healthy* with the
+`docker compose ps` command.
 
 Then, open a second terminal and run:
 
 ```
 docker compose exec linuxfr.org bin/rails db:setup
 ```
 
-Finally, the environment is ready and you can open [http://dlfp.lo](http://dlfp.lo)
+Finally, the environment is ready and you can open [http://dlfp.lo:9000](http://dlfp.lo:9000)
 in your favorite browser.
 
-Notes:
-
-1. to be able to access this URL, you'll need to add the following line
-  into the `/etc/hosts` file of your machine:
-  
-  ```
-  127.0.0.1 dlfp.lo image.dlfp.lo
-  ```
-
-2. for [rootless containers](https://rootlesscontaine.rs/), you'll need
-  to allow standard users to listen on ports less than 1024
-  (this is needed because linuxfr use port 80 and 443):
-
-  ```sh
-  sudo sysctl net.ipv4.ip_unprivileged_port_start=80
-  ```
-
-
 Personalize configuration
 =========================
 
@@ -68,16 +61,14 @@ If you want, you can change the domain names used by the LinuxFr.org
 web application. To do this, you can setup `DOMAIN` and `IMAGE_DOMAIN`
 variables in the `deployment/default.env` file.
 
-You can also configure your own Redis service and your own MySQL
-service.
-
-If you want to change the application port and/or other configurations, you can
-[override](https://docs.docker.com/compose/extends/)
-the docker compose configuration (in particular the `nginx` service for
-the port).
+Within the same file, you can update the HTTP listening ports by updating the
+`DOMAIN_HTTP_PORT` and `IMAGE_DOMAIN_HTTP_PORT` variables (both are set to 
+`9000` by default). If you modify them, don't forget to add the new values as
+published ports for the `nginx` service in the `compose.yaml` file (they have
+to target the `8080` container port).
 
-Notice, that if LinuxFr.org doesn't run on port 80, the image cache
-service won't work well and so you won't be able to see images in the news.
+You can also configure your own Redis service and your own MySQL
+service by updating environment variables in the same file.
 
 Test modifications
 ==================

INSTALL.md

@@ -131,11 +131,20 @@ Additionally, you run the boards within another terminal:
 
 This extra step isn't really needed to be able to use LinuxFr.org.
 
-In the `config/environments/development.rb` file, there are two domains set
-inside variables `MY_DOMAIN` and `IMG_DOMAIN`.
-By default both domains are `dlfp.lo`.
+In the `config/environments/development.rb` file, there are these variables:
 
-You'll find this domain inside some documents like emails to confirm user
+1. `MY_DOMAIN` and `IMG_DOMAIN` which define the domain name for the LinuxFr
+    service and the image caching service.
+    By default both domain names are `dlfp.lo`.
+
+2. `MY_PUBLIC_URL` and `IMG_PUBLIC_PORT` which define the public HTTP port for
+    both services.
+    By default both ports are `80`.
+
+These two set of variables are used to build the public url of the two
+services. By default both public urls are `http://dlfp.lo`.
+
+You'll find this public url inside some documents like emails to confirm user
 subscription. To simplify your usage of LinuxFr.org, you should consider
 install a website locally using this domain name.
 

app/controllers/admin/stylesheets_controller.rb

@@ -6,7 +6,7 @@ def show
 
   def create
     Stylesheet.temporary(current_account, params[:url]) do
-      redirect_to "/" + Stylesheet.capture("http://#{MY_DOMAIN}/", cookies)
+      redirect_to "/" + Stylesheet.capture("#{MY_PUBLIC_URL}/", cookies)
     end
   end
 

app/helpers/atom_helper.rb

@@ -5,7 +5,7 @@ def atom_comments_link(content, url)
     str = <<-EOS
     <p>
       <strong>Commentaires :</strong>
-      <a href=\"//#{MY_DOMAIN}/nodes/#{content.node.id}/comments.atom\">voir le flux Atom</a>
+      <a href=\"#{MY_PUBLIC_URL}/nodes/#{content.node.id}/comments.atom\">voir le flux Atom</a>
       <a href=\"#{url}#comments\">ouvrir dans le navigateur</a>
     </p>
     EOS

app/models/diary.rb

@@ -75,7 +75,7 @@ def convert
       @news.save!
       $redis.set "convert/#{@news.id}", self.id
       @news.node.update_column(:cc_licensed, node.cc_licensed)
-      @news.links.create title: "Journal à l’origine de la dépêche", url: "https://#{MY_DOMAIN}/users/#{owner.to_param}/journaux/#{to_param}", lang: "fr"
+      @news.links.create title: "Journal à l’origine de la dépêche", url: "#{MY_PUBLIC_DOMAIN}/users/#{owner.to_param}/journaux/#{to_param}", lang: "fr"
       @news
     end
   end

app/models/image.rb

@@ -67,7 +67,7 @@ def src(type="img")
     return link if internal_link?
     return E403 if blacklisted?
     register_in_redis
-    "//#{IMG_DOMAIN}/#{type}/#{encoded_link}/#{filename}"
+    "#{IMG_PUBLIC_URL}/#{type}/#{encoded_link}/#{filename}"
   end
 
   def src_attr

app/models/node.rb

@@ -170,7 +170,7 @@ def set_taglist(list, user_id)
         if tag.new_record?
           tag.save!
           user = User.find(user_id)
-          Board.amr_notification("L’étiquette #{tagname} https://#{MY_DOMAIN}/tags/#{tagname}/public vient d’être créée par #{user.name} https://#{MY_DOMAIN}/users/#{user.cached_slug}")
+          Board.amr_notification("L’étiquette #{tagname} #{MY_PUBLIC_URL}/tags/#{tagname}/public vient d’être créée par #{user.name} #{MY_PUBLIC_URL}/users/#{user.cached_slug}")
         end
         taggings.create(tag_id: tag.id, user_id: user_id)
       end

app/uploaders/avatar_uploader.rb

@@ -3,7 +3,7 @@
 class AvatarUploader < CarrierWave::Uploader::Base
 
   AVATAR_SIZE = 64
-  DEFAULT_AVATAR_URL = "//#{MY_DOMAIN}/images/default-avatar.svg"
+  DEFAULT_AVATAR_URL = "#{MY_PUBLIC_URL}/images/default-avatar.svg"
 
   include CarrierWave::MiniMagick
   process resize_and_pad: [AVATAR_SIZE, AVATAR_SIZE]
@@ -13,7 +13,7 @@ def base_dir
   end
 
   def url
-    super.sub(base_dir.to_s, "//#{IMG_DOMAIN}")
+    super.sub(base_dir.to_s, "#{IMG_PUBLIC_URL}")
   end
 
   def store_dir

app/uploaders/stylesheet_uploader.rb

@@ -6,7 +6,7 @@ def base_dir
   end
 
   def url
-    super.sub(base_dir.to_s, "//#{IMG_DOMAIN}")
+    super.sub(base_dir.to_s, "#{IMG_PUBLIC_URL}")
   end
 
   def store_dir

app/views/bookmarks/_bookmark.atom.builder

@@ -8,5 +8,5 @@ feed.entry(bookmark, :url => url) do |entry|
   bookmark.node.popular_tags.each do |tag|
     entry.category(:term => tag.name)
   end
-  entry.wfw :commentRss, "https://#{MY_DOMAIN}/nodes/#{bookmark.node.id}/comments.atom"
+  entry.wfw :commentRss, "#{MY_PUBLIC_URL}/nodes/#{bookmark.node.id}/comments.atom"
 end