1. What is the problem? Be very detailed.
I am following the Digital Ocean instructions to install Central and I am at the point of installing Central on it on my server. For some reason commands such as 'git submodule update -i' and 'mv .env.template .env' are both saying command not found. - I am using the root account. I am a newbie to linux and ODK
2. What app or server are you using and on what device and operating system? Include version numbers.
AWS EC2 instance running Ubuntu 20.4.2. I have installed Docker engine and compose.
3. What you have you tried to fix the problem?
Looking for alternative instructions but most seem to suggest the same thing.
4. What steps can we take to reproduce the problem?
5. Anything else we should know or have? If you have a test form or screenshots or logs, attach below.
You need to follow the complete instructions for Getting and Setting Up Central. Before running git submodule update -i you need to run git clone https://github.com/getodk/central and then cd central. The last line in your screenshot should show the below after you the run the cd central command.
I did run that command previously and am now trying again. Sadly, I am getting the same issue where the command does not work. I don't understand why. This worked smoothly with my Digital Ocean installation but in EC2 I keep having this issue. Could it possibly be because of an issue with Docker Engine or Docker Compose? I have followed the instructions to install them but as you can see I am having this issue.
Thanks for your response. I didn't install Docker. I chose an AMI with Docker on Ubuntu 20. I have tried running it twice from scratch and have the same results. Perhaps it is defective in some way?! I may try one without Docker to see what happens. Here is a screenshot of what happens when I run your commands. Thanks. Tony
I have setup an Ubuntu AMI with no docker. Installed Docker Engine and Compose but yet I still have the same issue installing central with no such file or directory error. Is there another way I can install it that you know of?
Hi @Saad@yanokwa I started again and for whatever reason it is now working. I am online and can browse to the webpage and login as myself.
Where I am struggling now is with creating a web user. I have added my AWS SES details into the config file and I know the details are correct and working because I am using them elsewhere. For some reason I am seeing error 500 code. Do you know if it possible to see in the logs why this is not working? Outbound traffic on the EC2 instance is open as default.
It is great to hear from you after a long time. Thanks so much for the support it worked perfectly. All installation processes went well till the end and checked the status of the ODK central and the service is up. However, cannot access central on the web browser. I even tried to access using the IP of my ODK central and no luck! any suggestion?
Thanks for all your suggestions! @iamnarendrasingh DNS records are perfectly configured and I am using a proper domain name as I have some unused domains. I created A record.
@Saad thanks, I noticed that my 443 port was not open.
I have a question as I am trying to install it on AWS lightsail on Ubuntu 20.04. Since the documentation does not cover AWS installation sequentially I am following this instruction and one thing I found completely different in this instruction from the ODK documentation, which is
I did not notice that in ODK documentation. Is this step mandatory? In fact, this instruction ODK was installed inside the data directory.
I am quite lost. Need help, friends, to get out of this. If could get a good step-by-step guide to walk through this installation process will be very helpful. There are too many mismatches between instructions in documents to install in docker and ODK central.
Thanks so much for all the support and thanks in advance for future support.
@A.N.M_AL-IMRAN In general, the only instructions we recommend are the ones on the docs site because those are the only instructions we verify and keep up-to-date. I hear you that we don't have the complete AWS instructions and that's something that we'll be improving soon.
As to configuring the Docker data root folder, that is typically not necessary. Or rather, you only need to do that if your boot volume is tiny and you'd like that data on another volume.