nickchubb/dockerman

🐳 A Server-side Docker Controller made with React and Node.js

Nick Chubb 👨‍💻

Website | LinkedIn | Resume | Send me an email!

👋 Hi, I am recent graduate with a degree in Computer Science & Molecular Biology and aspiring Full-Stack Developer.

I am currently seeking Front-end/Full-stack dev positions starting immediately, please don't hestitate to reach out if you have an opportunity where you think I would be a great fit!

I have an avid interest in the field of software engineering, and currently I am working on furthering my own software skills by developing my own React web applications. I find the field of biotech extremely interesting and I am particularly drawn to the comparisons that can be drawn between cellular machinery and computer systems, and how they influence each other.

In my free time I enjoy reading, going to the gym, and spending time with friends and family.

Click Here to see my Resume

👇 Check out my favourite projects below 👇

dockerman's Issues

Add ability for served routes to be password protected

Implement container screen

Features could include:

• Ports
• Container log
• Notes
• Link to served endpoint
• Rebuild (if from repo)
• Access to non-admin users

Docker tab with buttons for fixing docker errors

For example, common problems include restarting docker, fixing docker privileges.

Config in database

Config should be stored in database instead of JSON file

Add github link to bottom bar

Fix prune containers not working

Fix serve port bug.

Update favicon and title

Create api methods for react api helpers

Refactor so each method using fetch uses the same function, with the potential debug parameter.

eg. getReq('/api/container', true);
...

Link to served endpoint should only be active when container is served.

Feature to create new containers from directory

Big feature.

Allows the user to copy directory from local machine to the server and creates a container based on a template Dockerfile. If git is included in the repo include the option to git pull and rebuild the container.

Look for build.sh file in the directory and allow option to rebuild the container if it exists. Will probably have to include directory for containers in the database, how to do this?

Implement main top-bar control panel

Features:

• docker prune -a
• docker images prune -a
• ...

Implement popup confirmation message

Separate different APIs into their own classes

Add re-install config option when do config file is displayed.

No config div in DisplayConfig already has the a link which should be used. When clicked it will make a new copy of the default config to config.json.

Fix container restart button functionality

Updating logs to use pages

Add License

Investigate issues with serving containers form

Warnings when memory or disk space running low

Alerts/popups and maybe log it too?

Serve subdomains

Refer to: https://github.com/bmullan91/express-subdomain

• Add form field for subdomain in ServeForm
• Update router to serve subdomains in backend
• Update service database in backend to include subdomain

Performance bug when starting/stopping/restarting all containers

When using the buttons to start/stop/etc all containers, the front end will continuously send inspect HTTP requests a few times a second until the page is refreshed.

Serve private routes

Display more system info

Ram, total space on HD, etc?

Sort running containers to top

Alert on successful serve/etc

Notification on unviewed log messages

Implement Loading Page

System info should be stream

Especially memory and disk space

Add useAuth parameter to config

Will disable the route component which displays login page when auth is turned off

Allow container-specific info/control screen to be shared with un-authenticated users

To allow un-authenticated users the ability to start/stop a specific container and view its logs.

I believe the best way to do this would be to include a new middleware for the express router which uses nickchubb.ca/dockerman/share/container/{id} as the endpoint, before the current authentication middleware. When a request comes in for a /dockerman/share/container/{id} endpoint, the backend will check if the container exists and if it is saved as shared in the db. If the container is marked as shared it will return the container info screen and no other information. To do this it will have to have a share page like login or main so as to separate the pages and avoid any potential un-intended security leaks (via API calls).

Steps

• Share button on container info screen
• Add 'shared' parameter to service db
• Rework router code to include shared endpoint which shares containers if the shared parameter is set
• Work out bugs with API calls for operating container, since it might be hard to make sure the user can start and stop the container while being unauthorized.

Serving (or unserving) a container should log

Calculate and log space saved when pruning/removing containers

Update README.md

Add deployment info, features, contact.