You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Production deployment using letsencrypt certs
* Fixing problems with variables
* Fixed error on development provision
Sort of typo when development provision used
* Using getopt to get provision.sh parameters
* laguage-pack after apt-get update
* Fixing travis file for new provisioning
* Using custom unison location
* Fixing issues from comments
* Check arguments with a list
* Normal color variable name and display code dirs
Copy file name to clipboardExpand all lines: README.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ Note that if you don't want to use the Vagrant VM (not recommended), you can pro
48
48
sudo apt-get install git
49
49
git clone https://github.com/facebook/fbctf
50
50
cd fbctf
51
-
./extra/provision.sh dev $PWD
51
+
./extra/provision.sh -m dev -s $PWD
52
52
```
53
53
54
54
### Production
@@ -59,7 +59,7 @@ The target system needs to be 64 bit Ubuntu 14.04. Run the following commands:
59
59
sudo apt-get install git
60
60
git clone https://github.com/facebook/fbctf
61
61
cd fbctf
62
-
./extra/provision.sh prod $PWD
62
+
./extra/provision.sh -m prod -s$PWD
63
63
```
64
64
65
65
*Note*: Because this is a production environment, the password will be randomly generated when the provision script finishes. This ensures that you can't forget to change the default password after provisioning. Make sure to watch the very end of the provision script, as the password will be printed out. It will not be stored elsewhere, so either keep track of it or change it. In order to change the password, run the following command:
This will set the password to 'new_password', assuming the database user/password is ctf/ctf and the database name is fbctf (these are the defaults).
72
72
73
-
The provision script will place the code in the `/var/www/fbctf` directory, install all dependencies, and start the server. In order to run in production mode, we require that you use SSL. The provision script will ask you for your SSL certificate's CSR and key files. More information on setting up SSL is specific in the next session, but note that if you are just testing out the platform and not running it production, you want to use the instructions listed in the Development section below, as this takes care generating certificates for you. We will support Let's Encrypt in the future.
73
+
By default, the provision script will place the code in the `/var/www/fbctf` directory, install all dependencies, and start the server. In order to run in production mode, we require that you use SSL. You can choose between generating new self-signed, using your own or generate valid SSL certificates using [Let's Encrypt](https://letsencrypt.org/). The provision script uses [certbot](https://certbot.eff.org/) to assist with the generation of valid SSL certificates. Use the help to see all the available options with the command:
74
+
75
+
```
76
+
./extra/provision -h
77
+
```
74
78
75
79
Once you've provisioned the VM, go to the URL/IP of the server. Click the "Login" link at the top right, enter the admin credentials, and you'll be redirected to the admin page. Enter the credentials you received at the end of the provision script to log in.
cat "$__path/extra/nginx.conf"| sed "s|CTFPATH|$__path/src|g"| sed "s|CER_FILE|$__cert|g"| sed "s|KEY_FILE|$__key|g"| sed "s|DHPARAM_FILE|$__dhparam|g"| sudo tee /etc/nginx/sites-available/fbctf.conf
0 commit comments