filp · March 5, 2018 14:20 · Jun 8, 2017 · Jun 8, 2017 · Jun 8, 2017 · May 15, 2017
diff --git a/syseng-project.md b/syseng-project.md
@@ -24,4 +24,4 @@ SFTP server & notification system, by combining two containers:
   - password: `impraise`
 - Remember to document your Dockerfile(s) and other components of your project appropriately!
 - We expect the submitted code to be production ready wherever feasible.  
-    **IMPORTANT** any areas where your project fails short of production readiness, please submit a short note explaining the steps you'd take to make it so.
+    **IMPORTANT** any areas where your project falls short of production readiness, please submit a short note explaining the steps you'd take to make it so.
diff --git a/syseng-project.md b/syseng-project.md
@@ -23,5 +23,5 @@ SFTP server & notification system, by combining two containers:
   - username: `impraise`
   - password: `impraise`
 - Remember to document your Dockerfile(s) and other components of your project appropriately!
-- We expect the submitted code to be production ready wherever feasible.
+- We expect the submitted code to be production ready wherever feasible.  
     **IMPORTANT** any areas where your project fails short of production readiness, please submit a short note explaining the steps you'd take to make it so.
diff --git a/syseng-project.md b/syseng-project.md
@@ -22,4 +22,6 @@ SFTP server & notification system, by combining two containers:
 - The SFTP service should accept the following credentials to connect:
   - username: `impraise`
   - password: `impraise`
-- Remember to document your Dockerfile(s) and other components of your project appropriately!
+- Remember to document your Dockerfile(s) and other components of your project appropriately!
+- We expect the submitted code to be production ready wherever feasible.
+    **IMPORTANT** any areas where your project fails short of production readiness, please submit a short note explaining the steps you'd take to make it so.
diff --git a/syseng-project.md b/syseng-project.md
@@ -1,14 +1,14 @@
 # Systems Engineer Project
 
-# SFTP watcher
+## SFTP watcher
 
 Using Docker, and other tools of your choice, your task is to build a simple
 SFTP server & notification system, by combining two containers:
 
 - Container A runs the SFTP server
 - Container B runs a script or service that monitors the directory served by Container A for new files, and prints their path to STDOUT
 
-## Rules
+### Rules
 
 - Both services (SFTP and the watcher) need to live in separate containers
 - You are free to use an existing Docker image for the SFTP server as your starting point (e.g https://github.com/atmoz/sftp)

diff --git a/syseng-project.md b/syseng-project.md
@@ -0,0 +1,25 @@
+# Systems Engineer Project
+
+# SFTP watcher
+
+Using Docker, and other tools of your choice, your task is to build a simple
+SFTP server & notification system, by combining two containers:
+
+- Container A runs the SFTP server
+- Container B runs a script or service that monitors the directory served by Container A for new files, and prints their path to STDOUT
+
+## Rules
+
+- Both services (SFTP and the watcher) need to live in separate containers
+- You are free to use an existing Docker image for the SFTP server as your starting point (e.g https://github.com/atmoz/sftp)
+- You are free to setup the Docker container for the watcher service however you'd like, but you must build it yourself:
+  - Pick any language you're comfortable with (Bash is fine too)
+  - You are free to use a base Docker image for the language you're using as the starting point (e.g https://hub.docker.com/_/ruby/ if you were to use ruby)
+- Use Docker volumes to share a directory between the SFTP and watcher containers
+- The watcher service should print the full path of new files in the directory (from the time the service starts)
+- The project should be able to be started from a single command
+  - You may write your own starter script, use docker-compose, or other tools of your choosing
+- The SFTP service should accept the following credentials to connect:
+  - username: `impraise`
+  - password: `impraise`
+- Remember to document your Dockerfile(s) and other components of your project appropriately!
No results found