A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
I’m trying to connect one droplet with a wordpress app to another with a nodejs app, lets say a chat.
https://example.com would be the wordpress app. I want that when someone enter to https://example.com/chat, he or she enters to the nodejs app. how could i connect both apps behind a load balancer and a database?
This should help:
Make sure all three droplets have private networking enabled so Nginx proxying happens on those internal networks. In your Nginx vhost definition you’ll have two “location” blocks, one for the root example.com/ and one for the chat app example.com/chat.
Cheers
carrierwave shows examples using S3, RackSpace, and Google storage. Is it possible to setup a similar thing with digital ocean?
I've reported this as an issue, but support is being slow to respond, and I wondered if anyone else had seen this issue. Under certain circumstances, my load balancers are *partly* losing connectivity with droplets. They end up being able to run their health checks only from one IP address, where normally with a healthy droplet, they use two. This means the droplet is being flagged as "unhealthy" and "down" when it is in fact up, and responding correctly. It is the load balancer that seems to be faulty. Has anyone else seen this? Or, better, have an idea what to do about it? For me, load balancers are not proving stable enough for production use. Once this has happened there seems to be no resolution, short of re-provisioning the entire load balancer, which of course makes them a bit pointless. Removing and adding a droplet again has no effect, they remain 50% unhealthy (aka "down"). See droplet: aps1.staging.turalt.com as an example. It is attached a load balancer, and is correctly responding to heath tests, e.g.,: 10.137.232.60 - - [26/Oct/2018:14:41:05 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:12 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:12 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:15 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:22 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:22 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" On aps2.staging.turalt.com, by contrast the logs are: 10.137.240.198 - - [26/Oct/2018:14:41:56 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.240.198 - - [26/Oct/2018:14:41:56 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:57 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:57 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.240.198 - - [26/Oct/2018:14:41:57 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" 10.137.232.60 - - [26/Oct/2018:14:41:58 +0000] "GET /health HTTP/1.0" 200 71 "-" "-" I am using the API to update software by temporarily removing a droplet and then adding it again, so that might be a factor, but I have no evidence for it. This isn't happening with all droplets, but I haven't found a pattern yet.
In Ghost's preview the `inlinecode` looks fine but when I publish the blog post and load in Safari or Chrome, it shows up as plain text. Here's the post: https://linuxhowto.tech/managing-users-and-groups/ ## Adding new users While you can use `vipw` to edit the user configuration files, it is better to run `useradd`. `vim /etc/default/useradd` The output should look similar to this: ``` GROUP=100 HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel CREATE_MAIL_SPOOL=yes ``` ### Useradd examples * `useradd -c "Comment here" sarah -s /bin/bash` sets a comment (-c) and defines the default shell (-s) * `useradd bob -s /usr/sbin/nologin` sets `nologin` as the users's default shell because many users don't need shell access * `useradd -m -u 1201 -G ops,dev linda` adds user, adds home directory (-m), adds user to groups _ops_ and _dev_ (-G), assigns _UID 1201+ (-u) * `useradd` creates a locked account until you run `passwd user` ### The login configuration file The `/etc/login.defs` file sets the configuration for the for the _Shadow Password Suite._ The following are some of its most significant attributes: > * `MOTD_FILE`: Defines the file that is used as _message of the day_ file. In this file, you can include messages to be displayed after the user has successfully logged into the server. > * `ENV_PATH`: Defines the `$PATH` variable, a list of directories that should be searched for executable files after logging in. > * `PASS_MAX_DAYS`, `PASS_MIN_DAYS`, and `PASS_WARN_AGE`: Define the default password expiration properties when creating new users. > * `UID_MIN`: The first UID to use when creating new users. > * `CREATE_HOME`: Indicates whether or not to create a home directory for new users. > * `USERGROUPS_ENAB`: Set to yes to create a private group for all new users. That means that a new user has a group with the same name as the user as its default group. If set to no, all users are made a member of the group users. [^n] ### System-wide Bash shell startup files * `/etc/profile` runs system-wide environment variables and startup scripts * `/etc/bashrc` contains system-wide aliases and functions [^n] ### Bash shell personal startup files While creating a user, `useradd` copies the `/etc/skel` user environment configuration files to the new user's home directory. The following are the default configuration files: * `~/.bash_profile` contains personal environment variables and startup scripts * `~/.bashrc` contains personal aliases and functions * `~/.bash_logout` contains personal scripts to run on logout[^n] ## Using usermod to modify users These are a couple common use cases for `usermod`: * `usermod -g sales mike` adds _mike_ to sales as _primary_ group * `usermod -aG ops lisa` adds _lisa_ to ops as a *secondary* group ## Managing password properties Here are some example use cases for `passwd` and `chage`: * `chage -E 2018-12-31 bob` sets Bob's account to expire on a specific date * `chage -l linda` lists account aging information * `passwd -n 30 -x 90 lori -w 3` sets _minimum password age_ of 30 days, a _maximum password age_ of 90 days (-w), and starts _warning_ the user 3-days before the password expires (-w) ## Linux group management The `useradd` command creates a default _primary group_ with the same name as the user. When a user creates a file, the group owner will be set to that user's primary group. Users have access to files owned by their secondary groups. Use the `id` command to list a user's group memberships: `id linda` The output should look something like this: `uid=1002(linda) gid=1003(account) groups=1003(account),1001(sales)` A common use case for secondary groups is to share documents between departments with a file server. ## Creating groups To create a new group, you can use the `vigr` command to directly modify the `/etc/group` file or you can run the `groupadd` command. * `groupadd devs` adds a group called _dev_ * `groupadd -g 404 devproject` adds a group called _devproject_ with _Group ID (GUID) 404_ * `grep devproject /etc/group` to confirm that you successfully added a group ### Modifying group membership * `usermod -g 1003 frank` changes frank's **primary** group to account, assigning GUID of 1003 * `usermod -aG dev lori` adds account as a _secondary_ group for lori * `usermod -g sales anouk` changes anouk's _primary_ group to sales --------------------------------------- [^n]: Excerpt from Sander van Vugt's [Red Hat® RHCSA™/RHCE® 7 Cert Guide Premium Edition](http://www.sandervanvugt.com/book-red-hat-rhcsa-rhce-7-cert-guide/) [^n]: Derived from [Linux From Scratch](http://www.linuxfromscratch.org/blfs/view/5.1/postlfs/profile.html) [^n]: Derived from [Linux From Scratch](http://www.linuxfromscratch.org/blfs/view/5.1/postlfs/profile.html)
Is there anyway to remove from one region if it is on multiple regions and it does cost?