How do I install and enable my custom theme in OpenEdx's docker based DevStack?
I use comprehensive theming
I use docker on Linux
The LMS and CMS read many configuration settings from the container filesystem in the following locations:
/edx/app/edxapp/cms.env.json
/edx/app/edxapp/cms.auth.json
Since you are using docker DevStack, shell into LMS, CMS to find those files.
shell into LMS
make lms-shell
Shell into CMS
make studio-shell
You can create this directory at any location on a file system that is accessible to your Open edX installation. For example, you might place it at the root of the file system in a directory named /my-open-edx-themes.
Set the file permissions on the themes directory, and all of its subdirectories, to enable read+write permissions for the Ubuntu user.
sudo chown -R edxapp:edxapp /my-open-edx-themes
sudo chmod -R u+rw /my-open-edx-themes
For each Open edX component that you want to theme, set the
"ENABLE_COMPREHENSIVE_THEMING" = True
"DEFAULT_SITE_THEME": "Your-theme-name "
For LMS,
/edx/app/edxapp/lms.env.json
For Studio,
/edx/app/edxapp/cms.env.json
For the E-commerce,
/edx/etc/ecommerce.yml
And for each Open edX component that you want to apply a theme to, add the absolute path of the themes directory to the
COMPREHENSIVE_THEME_DIRS
configuration property.
For LMS and Studio,
"COMPREHENSIVE_THEME_DIRS": [
"/my-open-edx-themes/edx-platform"
]
For the E-commerce,
COMPREHENSIVE_THEME_DIRS: ["/my-open-edx-themes/ecommerce"]
Finally, Restart all servers.
For more info, please follow this documentation.
http://edx.readthedocs.io/projects/edx-installing-configuring-and-running/en/latest/configuration/changing_appearance/theming/enable_themes.html
Add comments if you have any additional questions.
I have a server that can only SSH using a non-admin username. I also have the root username and password for this server. I want to install some packages by bootstrapping this node. Is there a way to bootstrap this server and run the installations switching to root?
I ran the command,
knife bootstrap [NODE_IP] --ssh-user [NON-ROOT-USERNAME] --ssh-password [NON-ROOT-PASSWORD] --sudo --use-sudo-password --node-name [NODE_NAME] --run-list 'recipe[bootstrap_test]'
You would need user with sudo access to install packages which is different from running installations using root. Give the non-admin user sudo access in sudoers file. you can configure sudo access using command visudo.
Also see this thread
I am attempting to test the sample app provided by Bitnami in the Ruby Stack, I have placed the files in the htdocs folder:
and access the url http://(IP)/sample. The result is that the url is active but I do not have permission to access anything present as:
How can I alter the permissions for this sample app so I can access?
Bitnami developer here. If you want to deploy your application using Passenger, you can follow the next guide.
https://wiki.bitnami.com/Infrastructure_Stacks/BitNami_Ruby_Stack?highlight=ruby+stack#How_can_I_deploy_my_Rails_application.3f
Apart from that, if you want to deploy a new page using Apache, you have to give read privileges to Apache. You can run the following commands:
$ sudo chown -R bitnami:daemon /opt/bitnami/apache2/htdocs
$ sudo chmod -R g+r /opt/bitnami/apache2/htdocs
I hope this helps.
I'm using capistrano to deploy a rails web app. I want to give the deploy user on the webserver as few privileges as I can. I was able to do everything I need to do as a non-privileged user except restart the webserver.
I'm doing this on an ubuntu server, but this problem is not specific to my use case (rails, capistrano, deployment), and I've seen a lot of approaches to this problem that seem to involve poor security practices. Wondering whether others can vet my solution and advise whether it's secure?
First, not necessary, but I have no idea why /etc/init.d/nginx would need any (even read) access by other users. If they need to read it, make them become root (by sudo or other means), so I:
chmod 750 /etc/init.d/nginx
Since the ownership is owner root, group root (or can be set such with chown root:root /etc/init.d/nginx) only root, or a user properly sudo'ed, can read, change or run /etc/init.d/nginx, and I'm not going to give my deploy user any such broad rights. Instead, I'm only going to give the deploy user the specific sudo right to run the control script /etc/init.d/nginx. They will not be able to run an editor to edit it, because they will only have the ability to execute that script. That means that if a someone gets access to my box as the deploy user, they can restart and stop, etc, the nginx process, but they cannot do more, like change the script to do lots of other, evil things.
Specifically, I'm doing this:
visudo
visudo is a specific tool used to edit the sudoers file, and you have to have sudoer privileges to access it.
Using visudo, I add:
# Give deploy the right to control nginx
deploy ALL=NOPASSWD: /etc/init.d/nginx
Check the sudo man page, but as I understand this, the first column is the user being given the sudo rights, in this case, “deploy”. The ALL gives deploy access from all types of terminals/logins (for example, over ssh). The end, /etc/init.d/nginx, ONLY gives the deploy user root access to run /etc/init.d/nginx (and in this case, the NOPASSWD means without a password, which I need for an unattended deployment). The deploy user cannot edit the script to make it evil, they would need FULL sudo access to do that. In fact, no one can unless they have root access, in which case there's a bigger problem. (I tested that the user deploy could not edit the script after doing this, and so should you!)
What do you folks think? Does this work? Are there better ways to do this? My question is similar to this and this, but provides more explanation than I found there, sorry if it's too duplicative, if so, I'll delete it, though I'm also asking for different approaches.
The best practice is to use /etc/sudoers.d/myuser
The /etc/sudoers.d/ folder can contain multiple files that allow users to call stuff using sudo without being root.
The file usually contains a user and a list of commands that the user can run without having to specify a password. Such as
sudo service nginx restart
Note that we are running the command using sudo. Without the sudo the sudoers.d/myuser file will never be used.
An example of such a file is
myuser ALL=(ALL) NOPASSWD: /usr/sbin/service nginx start,/usr/sbin/service nginx stop,/usr/sbin/service nginx restart
This will allow the myuser user to call all start, stop and restart for the nginx service.
You could add another line with another service or continue to append them to the comma separated list, for more items to control.
Also make shure you have run the command below to secure things
chmod 0440 /etc/sudoers.d/myuser
This is also the way I start and stop services my own created upstart scripts that live in /etc/init
It can be worth checking that out if you want to be able to run your own services easily.
Instructions:
In all commands, replace myuser with the name of your user that you want to use to start, restart, and stop nginx without sudo.
Open sudoers file for your user:
$ sudo visudo -f /etc/sudoers.d/myuser
Editor will open. There you paste the following line:
$ myusername ALL=(ALL) NOPASSWD: /usr/sbin/service nginx start,/usr/sbin/service nginx stop,/usr/sbin/service nginx restart
Save by hitting ctrl+o. It will ask where you want to save, simply press enter to confirm the default. Then exit out of the editor with ctrl+x.
I'm trying to install OpenProject on OpenShift but I'm having difficulties in understanding the process. I've managed to create an OpenShift application and SSH into the domain, however I don't have permissions to download the zip file / create the folder as in the instructions.
I have to mention that my GIT/Ruby/Openshift knowledge is very limited.
Has anyone tried this before? Can you tell me if it's possible and how?
Thanks!
You'll want to ssh into your gear
$ rhc ssh -a
Then cd into the data dir
$ cd $OPENSHIFT_DATA_DIR
Wget your file
$ wget https://github.com/opf/openproject/archive/2.4.0.zip
I, despite this issue being so old, I would like to share my efforts. I also wanted to get OpenProject running on OpenShift. My way was to first get an initial POD running with root permissions to set things up with the WebUI and then run the individual services without root permissions.
Details can be found in this Github repository:
https://github.com/jngrb/openproject-openshift