User Tools
toolsandtechnologies:errigal-file-server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| toolsandtechnologies:errigal-file-server [2018/03/13 11:54] – adsilva | toolsandtechnologies:errigal-file-server [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | Errigal-File-Server | ||
| + | |||
| + | **Author**: Avi | ||
| + | \\ **Date**: 9th March 2018 | ||
| + | |||
| + | **Repo**: https:// | ||
| + | \\ **Requirement Doc**: https:// | ||
| + | |||
| + | Errigal-File-Server(EFS) is simple REST based file server that allows file operations and replication over multiple servers. | ||
| + | |||
| + | It basically allows operations on files such as GET, POST, DELETE and replicate these operations over multiple servers. | ||
| + | |||
| + | Deployment from scratch: | ||
| + | |||
| + | * Create the following Directory structure for a non-root user(example: | ||
| + | |||
| + | < | ||
| + | mkdir ~/ | ||
| + | mkdir ~/ | ||
| + | chmod -R 0777 ~/ | ||
| + | </ | ||
| + | |||
| + | copy the latest binary from Jenkins: | ||
| + | < | ||
| + | ~/ | ||
| + | </ | ||
| + | |||
| + | Copy the process control scripts from the Git Repo and it should look as follows: | ||
| + | < | ||
| + | ~/ | ||
| + | ~/ | ||
| + | ~/ | ||
| + | </ | ||
| + | |||
| + | Give them executable permission: | ||
| + | < | ||
| + | chmod +x ~/ | ||
| + | chmod +x ~/ | ||
| + | chmod +x ~/ | ||
| + | chmod +x ~/ | ||
| + | </ | ||
| + | |||
| + | Add the config file: ~/ | ||
| + | < | ||
| + | #No Trailing slash in Paths! | ||
| + | port: 9090 | ||
| + | local_server: | ||
| + | remote_servers: | ||
| + | - " | ||
| + | </ | ||
| + | |||
| + | Add the following line in the cron Job (crontab -e) for the non-root user that you used earlier(example: | ||
| + | < | ||
| + | */1 * * * * / | ||
| + | </ | ||
| + | |||
| + | EFS should start within the next minute and the cron job will also ensure that EFS stays up and running. | ||
| + | |||
| + | Similar procedure is followed on other App handler (Apps2). The only difference being, the config file will have the " | ||
Page Tools
