+ - CPU
+ - One should be enough
+
Depending on your number of users and instances you federate with, extra CPUs will be helpful.
+
+
+ - RAM
+ -
+ 512MB should be enough for Mobilizon, Nginx and PostgreSQL
+
Mobilizon will use at least around ~256MB and PostgreSQL and nginx can use ~20MB. Extra memory can improve tasks like compiling and building dependencies.
+
+
+ - Storage
+ - Depends how many users and events you have
+
A little space will be needed for Mobilizon and it's dependencies (damn you node_modules) themselves. Otherwise, storage usage will grow mostly with user's profile pics and pictures associated to events. Also the PostgreSQL database can start to weigh a bit after a while, depending on how many events you create and how many other instances you follow.
+
+
+ - Bandwidth
+ - Any bandwidth will do, but higher numbers will improve the experience for users and will help federation.
+
\ No newline at end of file
diff --git a/docs/administration/index.md b/docs/administration/index.md
index b83255996..f30ce63c9 100644
--- a/docs/administration/index.md
+++ b/docs/administration/index.md
@@ -77,9 +77,9 @@ yarn install
Finally, we can build the front-end (this can take a few seconds).
!!! warning
- Building front-end can consume up to 512MB of RAM by default. If it's too much or not sufficient for your setup, you can adjust the maximum memory used by prefixing the command with the following option:
+ Building front-end can consume up to 2048MB of RAM by default. If it's too much or not sufficient for your setup, you can adjust the maximum memory used by prefixing the command with the following option:
```
- NODE_OPTIONS=--max_old_space_size=4096
+ NODE_BUILD_MEMORY=1024
```
```bash
yarn run build
diff --git a/docs/administration/upgrading.md b/docs/administration/upgrading.md
index 7a0d06ec0..2d03cb29a 100644
--- a/docs/administration/upgrading.md
+++ b/docs/administration/upgrading.md
@@ -50,6 +50,11 @@ yarn install
```
### Rebuild Mobilizon's front-end
+!!! warning
+ Building front-end can consume up to 2048MB of RAM by default. If it's too much or not sufficient for your setup, you can adjust the maximum memory used by prefixing the command with the following option:
+ ```
+ NODE_BUILD_MEMORY=1024
+ ```
```bash
yarn run build
cd ../
diff --git a/js/vue.config.js b/js/vue.config.js
index e1ddbb831..7ed74eb13 100644
--- a/js/vue.config.js
+++ b/js/vue.config.js
@@ -1,10 +1,30 @@
const path = require("path");
+const ForkTsCheckerWebpackPlugin = require("fork-ts-checker-webpack-plugin");
module.exports = {
runtimeCompiler: true,
lintOnSave: true,
filenameHashing: true,
outputDir: path.resolve(__dirname, "../priv/static"),
+ configureWebpack: (config) => {
+ // Limit the used memory when building
+ // Source : https://stackoverflow.com/a/55810460/10204399
+ // get a reference to the existing ForkTsCheckerWebpackPlugin
+ const existingForkTsChecker = config.plugins.filter(
+ (p) => p instanceof ForkTsCheckerWebpackPlugin
+ )[0];
+
+ // remove the existing ForkTsCheckerWebpackPlugin
+ // so that we can replace it with our modified version
+ config.plugins = config.plugins.filter((p) => !(p instanceof ForkTsCheckerWebpackPlugin));
+
+ // copy the options from the original ForkTsCheckerWebpackPlugin
+ // instance and add the memoryLimit property
+ const forkTsCheckerOptions = existingForkTsChecker.options;
+ forkTsCheckerOptions.memoryLimit = process.env.NODE_BUILD_MEMORY || 2048;
+
+ config.plugins.push(new ForkTsCheckerWebpackPlugin(forkTsCheckerOptions));
+ },
// configureWebpack: {
// optimization: {
// splitChunks: {
diff --git a/lib/web/views/utils.ex b/lib/web/views/utils.ex
index 5fd5417d6..950efcd53 100644
--- a/lib/web/views/utils.ex
+++ b/lib/web/views/utils.ex
@@ -18,11 +18,8 @@ defmodule Mobilizon.Web.Views.Utils do
end
@spec replace_meta(String.t(), String.t()) :: String.t()
- # TODO: Find why it's different in dev/prod and during tests
defp replace_meta(index_content, tags) do
- index_content
- |> String.replace("