I have created a website and uploaded images in assets module. I want to store my images and website content in my local system for backup.
Does anyone know how to do that. Thank you.
You can use Jackrabbit DataStore in order to that, basically you need to specify a threshold and Jackrabbit will automatically store them in your local data store.
For more information, have a look at: https://wiki.apache.org/jackrabbit/DataStore
Cheers,
Related
I have a backup of the entire Wordpress folder of one of my old websites but, unfortunately, I forgot to also make a backup of the database for it. It's been years since the website expired so there's no way I can get the SQL file that way, and both Wayback Machine and Google don't seem to have any caches left of it (a tutorial I saw mentioned trying that way).
Is it still possible for me to get the website working for local use?
Yes and no, depending on what you are willing to do.
Is it still possible for me to get the website working for local use? No
If you have no database you will not have access to the Posts, Pages, Users, Options and all of the meta.
Is it still possible for me to get the website working for local use? Yes
If you create all of the database entries again to your satisfaction. You will still have all of the images you can re-upload to recreate the database entries for images. Then just re-create all of the pages and users as needed. Plugins may need to be disabled/reactivated/reinstalled and configured as well as your theme settings.
Try https://web.archive.org/ , you might be in luck there. Without sqldump its not much to do. If you had a cache plugin active, check if you have any snapshots.
I have a Wordpress website,
which contains more than 100,000 posts.
this is an informative site.
Data does not change once entered into the system.
Problem
As data is so much so it requires good server configuration to process the data, which is really costly for me. Right now the website is not popular so its out of my budget to keep it running with such a huge price.
Right now the DB is on AWS RDS and it has 4GB of Ram.
Query
Is there any way that I can store all the data on users local machine so I dont need to hit the DB again and again.
I have little idea that redux does it, but not sure if this is possible or not. Any other idea would also be appreciated.
If the website is static, the content can be offloaded to Amazon S3. This can provide much lower-cost hosting because Wordpress and the database only need to be turned on when adding new content.
Search the web for some solutions, such as:
amazon s3 | WordPress.org
How to move WordPress images to Amazon S3 – Free Solution! – Jozef Jarosciak Blog
Moving WordPress Media To The Cloud With Amazon S3 - WPMU DEV
I am making a WordPress website and I might create new builds. How will I keep back up or save my latest builds, I would prefer to use and manage builds through github. Is there a particular way that I can do it in WordPress?
Simple way to install this plugin and create your WordPress backup and download it :
https://wordpress.org/plugins/duplicator/
I used gitwatch to automatically commit new code to a Github repository. This included new uploads and new plugins. Just follow the ReadMe and it works pretty well.
This is an example of a website where I used this technique.
Words of Caution
Use .gitignore to exclude your wp-config.php file so that database credentials etc are not stored to github.
Be careful not to dump your database to the wordpress directly (which
would automatically commit it to Github).
Be careful of plugins
that write sensitive stuff to a file that might get committed.
I am aware of Kerchoff's law, or not attempting security through
obscurity, but I am not stupid about the risks of automatically
publishing all of your configuration publicly. The site above is not
a high profile complex site (and I generally like to think I know
what I'm doing). DO NOT do this at home if your website is handling
sensitive information or could be at risk of anything more targeted
than a general Wordpress security flaw dragnet on Google.
One partial solution to these concerns would be to just make the Git repository private.
Finally if you are dealing with European data you need to comply with GDPR
which means you need to be ready to scrub a file from Git history
using something like BFG
You are addressing two different things. For backups, there are WordPress backup plugins that you can use like updraft (here's the link: https://wordpress.org/plugins/updraftplus/). But when it comes to development workflow then GitHub is the right platform. If you want to know how to work in a live environment and how to push and pull the latest changes from local to live or vice versa
(to keep track) then this guide will help you. https://www.cloudways.com/blog/wordpress-github/
How can we go about transferring an existing wordpress website, with lots of images in wp-content/uploads folder.
I have been able to run a fresh wordpress install on GAE following this
https://developers.google.com/appengine/articles/wordpress
The part where I am stuck is how to transfer an existing website?
I don't think you will find a drag-and-drop way to transfer your current WordPress installation to AppEngine, at least not without a good deal of effort:
First, you need to manually create a migration/mapping from your current data store to an instance of CloudSQL.
Second, you need to (somehow) remap all the static files/images to either Blobstore or Google Cloud Storage as there are limits to the amount of static files you can upload to an App Engine app.
Third make sure all your existing plugins URL rules can be matched with AppEngine's routing mechanism.
I need a reference about staging on Drupal 7.
My requirements are:
Content Administrator can perform editing of content in STAGING instance
Can preview the changes without impacting the PROD server that visitor sees
Only when the admin says "DEPLOY/PUBLISH", the changes are pushed to PROD
Any suggestion about what module should I use? Thank you.
Why should this be a module at all?
Staging should be a different deployment with a separate database and url.
If you've crossed that option out because you haven't found a way to move across "build" information stored within the database, then look at the features module.
I'm not sure if there is a solution like that ready, you could try making something with the domain module where content administrators can publish only in staging domain and the admins can publish to all domains. http://drupal.org/project/domain
Edit: to elaborate further, admins could go to the node list and choose which nodes to publish into production, or edit the node and change the domain where that node is publishes.
Hope this helps.
If you just want to provide the ability to administrator to edit content without impacting live content, you can use the revisioning module : http://drupal.org/project/revisioning
No need for a separate staging server for that, it's the purpose of a cms after all.