I have been stuck with installing mutiple odoo 10n instances on a server with subdomain filtering, for example:
xxxx.mydomain.com: an odoo instance installed at /opt/xxxx/
yyyy.mydomain.com: an odoo instance installed at /opt/yyyy/
To be more specific, I already have an instance of odoo 8 running at opt/odoo/ on odoo.mydomain.com. Now I want to install an instance of odoo 10, with the idea as explained above. Already found a tutorial at https://www.rosehosting.com/blog/how-to-install-odoo-10-with-subdomain-filtering/ but it's for Ubuntu.
Run odoo 10 in different port and that's all.
And don't forget to make db filters
Related
I have rundeck 3.3.10 installed on my RedHat server , I want to upgrade to 4.0.1 community version.But I want to keep the older version intact, while I install and setup the latest version. Is it possible ,if yes what are the steps to achieve this ?
I checked on PagerDuty site but couldnt find the information i was looking for.
You can keep two instances in this way:
The first one installed from the RPM/repo listening to the port 4440 and the second one could be installed as a WAR (for example, in the /opt/rundeck directory) and listening to another port, e.g: 4441.
You can see in this answer how to configure the second instance.
But if you're looking to keep two RPM instances, the best way is to replicate the 4.0.1 upgrade in a virtual machine (like Vagrant) and later upgrade your main server.
NOTE: Don't connect both instances against the same database, I assume that you're creating a specific database for the 2nd instance.
I have created a Java Web application with Elastic Beanstalk using AWS CodeStar. The application works, no problem there. But the EC2 instance the Elastic Beanstalk provisioned is running Amazon Linux 1. I need to have Amazon Linux 2, because some of the things I want to install there run only on Amazon Linux 2. The AMI used for the instance is aws-elasticbeanstalk-amzn-2018.03.0.x86_64-tomcat8.5java8-hvm-202102251130.
When you are creating a project via CodeStar, you can only select instance type (I selected t3.micro for start). There is no way to select operating system. You also cannot specify OS in the EC2 console or Elastic Beanstalk console. Solution might be to select a different AMI in the Auto-scaling group, but I am not sure if the template provided by CodeStar will work on AL2, since it was built for AL1.
So my question is:
Is there an easy way to get a AL2 instance for a CodeStar project?
If the only solution is to specify AMI, which one should it be and how to make sure my project will work there?
There are two ways to change it, but I don't know if forcing EB platform version change won't break some CodeStar compatibilities. Anyway, you can give it a go, if you want.
First option, you can go to your source code repo, and open template.yml. Find line SolutionStackName: !Ref 'SolutionStackName' and change to which platform you want, e.g.:
SolutionStackName: 64bit Amazon Linux 2 v4.1.6 running Tomcat 8.5 Corretto 11
The change should trigger re-deployment of your CodeStar project and EB env.
Or second option, go to CodePiepline of your CodeStar project and edit Deploy stage's GenerateChangeSet action. In the Advanced settings of the action, got to Parameter overrides and "SolutionStackName":"64bit Amazon Linux 2018.03 v3.4.4 running Tomcat 8.5 Java 8", to what you want, e.g.:
"SolutionStackName":"64bit Amazon Linux 2 v4.1.6 running Tomcat 8.5 Corretto 11",
Please not that you may need also to add permissions to the role CodePipeline uses for CloudFormation. The name of the role can be found in GenerateChangeSet action details. Once you have the name, you can go to IAM console, and add missing permissions. In my test, I did try to find minimum needed permissions, so I just added bunch of them (bad practice):
AmazonEC2FullAccess
AdministratorAccess-AWSElasticBeanstalk
AWSCloudFormationFullAccess
Finally, the demo application that CodeStar uses probably will not work with the updated environment as it was designed for older EB platforms, not new ones.
Our web developer picked OctoberCMS to develop our new website (his skill). Unfortunately before completion he rapidly left us due to health reasons and is no longer available. His Ubuntu environment has some problems and we need it on CentOS 7 anyway. The rest of us are OctoberCMS newbies, but want to learn it.
We built a CentOS 7 VM and installed OctoberCMS and want to move his work over.
We can not find any instructions on how to "export" the work he has done thus far and import it into our new OctoberCMS.
He is using 10 plugins and 3 he developed. (I don't know if that is relevant)
Is there an easy way to do this or at least instructions?
We have been googling, youtubing, IRC'ing for a week and still at a loss.
Any help would be most appreciated.
There really isn't anything special you need to know about moving an OctoberCMS install to a new server compared to moving over any other PHP application.
I am assuming you know how to do the basics of setting up a LAMP stack, such as setting up a virtual host for the domain you want to host the site on and setting up a MySQL database and user/password to access the database. There are of course many variants on how you could accomplish this such as using a management tool like Plesk or cPanel, or just configuring the services manually via the command line.
1) Ensure your new server is running at least roughly the same version of Apache, MySQL, and PHP.
2) Copy over the directory that contains all of the web files from the old server into the document root for your domain on the new server.
3) Do a database dump from the old server and copy it to the new server. If possible, use the same database name and username and password as the old server. This way you don't have to worry about updating the configuration of the website.
4) Pull up the site and troubleshoot any errors that come up. It is helpful if OctoberCMS debug mode is on.
Following the above method will ensure that you have the exact same setup on your new server that the old server had. This will copy over all of the plugins, data, etc.
There are of course many complexities that can come up during a switch over like this, but this should at least get you started and you can come back to StackOverflow with some more specific hurdles.
Hope that helps.
I have a magento setup where I am using one box for apache server and one as mysql server.
I want to install redis in this installation. I am not sure how I can achieve that.
My questions are:
On which box should I install Redis?
Is there any step by step tutorial for such setup? As i am new to this.
How can I configure magento to use redis server?
Thanks in advance.
Since you are only using 1 frontend server, I would set it up on that as it will be faster and take additional load off the database network connection.
1.9 has the Cm_RedisSession module included in the codebase and it's a doddle to setup, take a look here for step by step instructions;
http://inchoo.net/magento/using-redis-cache-backend-and-session-storage-in-magento/
How can I update the new versions of application in my ubuntu machines in private subnet which are in Autoscaling. I am using cloudfromation script to bring up the entire set up. Can I include any script in cloudfromation template to do this? Please help.
There are a few ways to accomplish the upgrade. Many people use amazon's provided script, cfn-hup. The way I do it is different and is as follows:
When instance launches, have script install application from files fetched from S3
Update S3 with new version.
Use a script(or manually) to shutdown instances one at a time, waiting for autoscaling to bring them up with the new version installed.