NOTE: Do NOT access the
httpsversion of the above site. The API server does not currently have an SSL certificate, and so thehttpsclient will not be able to communicate with the API due to the Mixed Content policy implemented in browsers.
The API is seperately accessible here, for use with Postman or cURL. However it is recommended to use the heroku app linked before.
We are accepting contributions to Code-IT! Check out CONTRIBUTING.md to learn more. Make sure to read our docs to learn about the set up process.
Feel free to make an issue if you have any inquiry or doubt. Use the question label for this.
Code-IT RCE is a service that provides a remote environment to run your code in. Execution occurs in a containerized space. The API supports programming in 3 languages (Python, Javascript and C++), potentially extendable to support more.
This RCE project provides a basic API to execute programs on a remote server. Basic code validation is performed to prevent possibly malicious code.
The client application, linked above, is available to access the API. It enables live sharing of your work through realtime communication with the server, aimed towards interview sessions. Each user obtains a sessionId key. Users can join another session by entering the other session's ID. Joining a session permits you to observe the session in read-only mode, only the session creator can edit the code and input.
- Sandboxed code execution on a remote server. Users can program in 3 languages without any local set up.
- Client app that incorporates all the features - Provides an easy and practical way to use the service. Locally caches user input for ease of use.
- Code validation - Dangerous libraries that can allow malicious execution are invalidated through /regex/ checks, and code containing such libraries are not executed.
- Live sessions. Each user can access and share their session's ID through the
sessionmenu in the navbar - Users can paste a session ID to join someone else's room from the same. (Only available through the client app)
User set up for this project is not required, as a deployed version can be accessed through the client app (linked at the top).
However if you wish to set the project up yourself, documentation has been provided in the docs folder. Check out DOCS.md for a detailed reference. It describes local machine setup and service functioning. Read SERVER.md for documentation on deployment.
This RCE project combines various different technologies:
-
Node and Express - Server and Executer services are written using these
-
React - Client application is written with React
-
Docker/docker-compose - Containerising of the services and providing an isolated sandbox for code execution
-
Bash scripting - Convinience scripts for environment setup and project execution
-
Socket.io - Websocket to implement live sharing feature
The API accepts POST requests at the localhost:9000/code or http://13.235.81.188/code endpoint.
-
key <String>- A random string to uniquely identify each request. This string should function as a valid Linux file name, for reasons mentioned in the documentation. When using the client app, the key also serves as the session ID. -
language <String>- Represents the programming language to be used. Its value is identical to the file extension used by the language, as shown in the next section. -
code <String>- User provided code/program. Content is written to the source file to be executed. -
input <String>- User provided input for their code. It functions as the STDIN value for the executor
-
Python3 (use: py)
-
C++ (use: cpp)
-
Node/Javascript (use: js)
Currently, code validation takes place by selectively rejecting or accepting libraries depending on the language. The list of libraries of concern are listed below
os | subprocess | shlex | xml | pickle
iostream | algorithm | stdio | cstdio | vector | math | cmath | cstring | string |
deque | iomanip | iterator | map | queue | set | stack | conio | ctype
readline | buffer | string_decoder | timers | stream | util