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
Copy file name to clipboardExpand all lines: README.md
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ And some random odds and ends:
80
80
81
81
## Tests
82
82
83
-
If you have `make` and and recent `perl` installed (you almost certainly do), you can run the tests using:
83
+
If you have `make` and and recent `perl` installed (you almost certainly do, or if not see [Vagrant](#vagrant) and [Docker](#docker) sections below), you can run the tests using:
84
84
85
85
make test
86
86
@@ -99,3 +99,22 @@ If you don't want to mess with your local development environment, you can run t
99
99
vagrant ssh
100
100
cd /vagrant
101
101
make test
102
+
103
+
## Docker
104
+
105
+
Similarly, Docker is an option for both local development and test running, but is not suitable for production use (really, REALLY don't use it for prod -- we (intentionally) do not have this configured securely). To build and run:
106
+
107
+
docker build -t flamework .
108
+
docker run -ti -p80:8081 -p443:4331 -v ~/dev/flamework:/mnt/flamework --name=flamework --rm flamework
109
+
110
+
Your local flamework copy should now be listening on ports `8081` and `4331`. Use `docker ps` to verify them. You'll need to edit <code>include/config.php</code> as usual. Since you mounted your local dev flamework directory into the container, any code changes you make should be reflected immediately.
111
+
112
+
Once the container is running, to run tests you can do:
When killing the container using either `CTRL+C` or `docker stop flamework`, the container will be removed and all data will be reset next run. This is useful for running tests.
0 commit comments