-In both dev and prod environments we have Node configured to run on port 3000, with Apache proxying it across to port 80. The reason for Apache is so that we can use other tech stacks alongside Node.
-
-macOS comes with an Apache installation built in. We just need to configure it a little bit.
-
-First, we’ll edit the main Apache configuration file.
-
-```
-sudo vim /private/etc/apache2/httpd.conf
-```
-
-The following individual lines each need to be uncommented:
-Finally, let’s restart Apache so it picks up the changes.
-
-```
-sudo apachectl restart
-```
-
-If you end up installing a macOS update you should go through the Apache configuration section again, as your Apache config in `httpd.conf` may have been restored to the default.
-
## MariaDB
Next we’ll set up a MariaDB user and a fresh database. We’ll start by opening up a console using the `mysql` command.
@@ -496,10 +430,11 @@
```json
{
- "baseDomain": "http://localhost",
+ "baseDomain": "http://localhost:3000",
"basePath": "/comm/",
- "baseRoutePath": "/",
- "https": false
+ "baseRoutePath": "/comm",
+ "https": false,
+ "proxy": "none"
}
```
@@ -513,13 +448,30 @@
```json
{
- "baseDomain": "http://localhost",
+ "baseDomain": "http://localhost:3000",
"basePath": "/commlanding/",
"baseRoutePath": "/commlanding/",
- "https": false
+ "https": false,
+ "proxy": "none"
}
```
+vim keyserver/facts/squadcal_url.json
+
+````
+
+Your `squadcal_url.json` file should look like this:
+
+```json
+{
+ "baseDomain": "http://localhost:3000",
+ "basePath": "/",
+ "baseRoutePath": "/",
+ "https": false,
+ "proxy": "none"
+}
+````
+
## MariaDB
The keyserver side needs to see some config files before things can work. The first is a config file with MariaDB details.