I have a auto-deploy REDMINE by Bitnami (ubuntu) on a AWS instance, I've installed AGILE Plugin follow this steps:
https://docs.bitnami.com/aws/apps/redmine/configuration/install-plugin-agile/
Agile plugin is proper installed, but i cant move issues on agile board
I trying to move issue card from a column to another, but not work, follow this steps :
https://www.redmineup.com/pages/help/agile/cannot-move-issues
I've grant permissions to bitnami user to this folders, with no results
permissons:
-rwxrwxrwx 1 bitnami daemon 0 Apr 6 2020 empty
drwxrwxrwx 5 bitnami bitnami 4096 Nov 10 18:08 redmine_agile
drwxrwxrwx 5 bitnami bitnami 4096 Nov 10 18:08 redmine_crm
Related
I am trying to host a shiny app on an AWS EC2 for the first time. I have been following this [tutorial] (https://www.charlesbordet.com/en/guide-shiny-aws/#3-how-to-configure-shiny-server).
I adjusted my sudo nano /etc/shiny-server/shiny-server.conf with sanitize_errors false; so the errors display at http://18.144.34.215:3838/. It seems I do not have the correct permission allocated to that folder from the shiny-server.
This is my first attempt at hosting a shiny app on EC2 and a bit lost from other posts I have found searching. What would be the correct commands to give permission to this folder?
Also, please let me know what info you need from me in order to understand this error better.
Here are my folder permission for 'RIBBiTR_DataRepository'
-rw-rwSr-- 1 ubuntu ubuntu 35149 Feb 1 21:32 LICENSE
-rw-rwSr-- 1 ubuntu ubuntu 10 Feb 1 21:32 README.md
drwxrwsrwx 5 ubuntu ubuntu 4096 Feb 1 21:38 RIBBiTR_DataRepository
-rw-rwSr-- 1 ubuntu ubuntu 205 Feb 1 21:32 db_forms.Rproj
drwxrwsr-x 2 ubuntu ubuntu 4096 Feb 1 21:32 misc
And to add, when I try to view the logs I receive a permission denied
ubuntu#ip-172-30-1-21:/var/log/shiny-server$ sudo tail RIBBiTR_DataRepository-shiny-20230201-215702-44689.log
su: ignoring --preserve-environment, it's mutually exclusive with --login
-bash: line 1: cd: /srv/shiny-server/db_forms/RIBBiTR_DataRepository: Permission denied
The issue was in my shiny-server.conf file. I updated the file with a user group, run_as ubuntu;
How do I configure 2nd site on Bitnami Lightsail Wordpress to host a second web site?
I just started with AWS Lightsail and I have a wordpress site running on it without an issues.. I site does not have alot of users so I would like to add my 2nd workpress site to it.
The first thing I am trying is to point my apache to a 2nd folder using vhost. I want into
/home/bitnami/stack/apache/conf/vhosts
and copied the following two files and edited the pathed on the new sites
-rw-r--r-- 1 root root 1830 Jan 11 17:19 wordpress-https-vhost.conf
-rw-r--r-- 1 root root 1998 Jan 11 17:19 wordpress-vhost.conf
I then restarted apache
sudo /opt/bitnami/ctlscript.sh restart apache
both domain names are still going to the same location.. what am I missing
I have static folder serving the files on uwsgi.
/user/app/static/
lrwxrwxrwx 1 root root 23 Oct 13 09:40 _out -> /usr/src/app/_mat/_out/
drwxr-xr-x 8 root root 4096 Oct 13 09:49 assets
drwxr-xr-x 8 root root 4096 Oct 13 09:40 pages
in this case, the imagefiles under assets can be appeared correctly,
however the image files under _out can not be accessed.(404 error occurs)
static/assets/test.png is ok
static/_out/test.png returns 404 error
/usr/src/app/_mat/ are on the aws EFS.
I checked the permissions.
Generally speaking, does symbolic link work under web server?
I have an issue where a few tools, Portainer for example, can't find the docker socket on AWS.
I have some setup scripts that were run to set various containers.
On MacOS, it works without problems.
On a CentOS box, no problem as well.
On CentOS / AWS, containers cannot connect to the docker socket.
I am talking about a local unsecured connection to /var/run/docker.sock
What could be different on AWS?
I can see the socket:
➜ run ls -ld /var/run/docker*
drwxr-xr-x 8 root root 200 Nov 27 14:04 /var/run/docker
-rw-r--r-- 1 root root 4 Nov 27 14:03 /var/run/docker.pid
srw-rw-r-- 1 root docker 0 Nov 27 14:03 /var/run/docker.sock
I've changed this post from a question regarding an error I was getting (which BTW received no answers) into actual instructions on HOW-TO integrate cocos2d-x version 2.2.5 into Marmalade (because none could be found online). This should prove valuable to new Marmalade developers and experienced developers alike. Marmalade comes with an older and (oh dear, a) BETA version of Cocos2dx (version 2.1.0 Beta3 as of this post) and we want to upgrade that. These instructions apply to Mac OSX systems but a similar approach (minus directory soft-linking) can be applied to Win32 systems as well.
Assuming you've already downloaded and installed Marmalade.
Download Cocos2dx version 2.2.5 (or the latest 2.x branch)
Open the Applications folder (from GUI) and scroll down to Marmalade, right-click on Marmalade and choose Show Package Contents.
Drill down the following path ./Contents/modules/third_party/
Rename the cocos2dx directory to cocos2dx_2.1.0_beta3 (you can tell what version of cocos2dx came with Marmalade by opening the ./cocos2dx/cocos2dx/ folders and viewing the cocoos2d.cpp file.)
Create a new folder called cocos2dx_2.2.5.
Copy the following folders from your cocos2dx 2.2.5 download: cocos2dx, CocosDenshion, extenstions, external, licenses, scripting, tools.
Paste those into the new cocos2dx_2.2.5 folder.
Open Terminal and cd into /Applications/Marmalade.app/Contents/modules/third_party
Create a soft-link to the new cocos2dx_2.2.5 directory: ln -s cocos2dx_2.2.5/ cocos2dx (note: for Win32 users, simply rename the new directory to cocos2dx).
Performing a ls -l under /Applications/Marmalade.app/Contents/modules/third_party should now yield something that looks similar to the following:
drwxr-xr-x# 8 user admin 272 Oct 1 08:35 Photon
drwxr-xr-x# 6 user admin 204 Oct 1 08:35 c-ares
lrwxr-xr-x 1 user admin 15 Nov 5 23:32 cocos2dx -> cocos2dx_2.2.5/ <-- soft-link
drwxr-xr-x# 9 user admin 306 Oct 1 08:35 cocos2dx_2.1.0_beta3 <-- this
drwxr-xr-x 9 user admin 306 Nov 5 23:28 cocos2dx_2.2.5 <-- this
drwxr-xr-x# 7 user admin 238 Oct 1 08:35 curl
drwxr-xr-x# 8 user admin 272 Oct 1 08:35 expat
drwxr-xr-x# 6 user admin 204 Oct 1 08:35 gaf
drwxr-xr-x# 11 user admin 374 Oct 1 08:35 jsoncpp
drwxr-xr-x# 8 user admin 272 Oct 1 08:35 libjpeg
drwxr-xr-x# 6 user admin 204 Oct 1 08:35 libpng
drwxr-xr-x# 8 user admin 272 Oct 1 08:35 lua
drwxr-xr-x# 7 user admin 238 Oct 1 08:35 ode
drwxr-xr-x# 12 user admin 408 Oct 1 08:35 openquick
drwxr-xr-x# 12 user admin 408 Oct 1 08:35 openssl
drwxr-xr-x# 7 user admin 238 Oct 1 08:35 sqlite
drwxr-xr-x# 6 user admin 204 Oct 1 08:35 tiniconv
drwxr-xr-x# 10 user admin 340 Oct 1 08:35 tinyxml
drwxr-xr-x# 6 user admin 204 Oct 1 08:35 twitcurl
drwxr-xr-x# 7 user admin 238 Oct 1 08:35 zlib
From now on Marmalade will use the latest 2.x release of Cocos2dx. Simply change the soft-link to point to a newer version when it comes out, or an older version if you have problems.
Hope it helps.
To do something in a more Marmalade friendly way, I would suggest the following:
DO NOT place this code in your Marmalade SDK area - it just means that everytime a new SDK comes along you have to hack things, and it won't work out of the box.
Instead add something the following near the top of the mkb for the programs you want to use:
option module_path="whereeverIputcoscos/cocos2dx_2.2.5"
filling in the correct path. Not tried it, but this is the basic method. Once you've got that setup, it will use it without you having to fiddle with any SDK first.