First of all, I'm sorry if this is pretty stupid question for you, I was searching the web for the answer, but unfortunately couldn't find complex one.
Recently I discovered not so new, but still cool stuff like SCSS, Pug, LiveReload, Gulp and all that automation stuff. I was really blown away, cause I've been like in a cave for past 2-3 years. So, the development for me is pretty easy and fast now, but I've got problem with production of this.
So, for example, I have to develop WordPress site. One year ago, I'd just run local server, install WordPress there, then I create a new template and customize it for customer needs. After that, I'd upload all of that on web-server (for FTP stuff I use Filezilla, if there's better tools - point me, please) and than, if needed, I'd open desired files from "Edit" menu in Filezilla, customize them, save - and that it's done, I can see the result in browser. I don't need local copy of the web-site on my computer (since some web-sites nowadays are pretty 'heavy').
Now, I don't know what to do with that automation stuff, cause it's all running with console and has to be compiled. So, in order to develop complex CMS-driven web-sites using automation tools, I need to always have latest copy on my local machine, and that send it again on web-server? What if customer, for example, decides to change the article or something on the web-site, when I sync my local copy with web-server, it'll be lost.
So, my main question, is there a way for me to create WordPress website using Gulp & Co and then easily update it later, via FTP client?
Related
I am looking for a simple, no frills, docker-compose based solution so I can start playing with some common tools, without having to devote lots of time into learning to configure the infrastructure. It should pull from the official images of the included projects, to make things super standardized and easy to move forward.
Ideally, I can have local directories mounted, so I can just edit my code directly, and have it served up through the container. Even better is to have the database stored similarly, in case I wind up liking it and want to port it into a project.
Edit:
Since it seems nobody gets it. The reasons for wanting this are:
No local installation of tools to pollute my development environment.
No rebuilding of containers as I change my code, learn, and test out features.
Not using any exotic features or special configuration, so official containers from the distributions should be sufficient.
Clean roadmap to scaling up to a real project. Acts as a template going forward.
Not spending time on tasks that are not relevant to the final goal (configuring a platform that may never be used).
It seems clear to me that a significant portion of development should use containerized runtimes for building/testing, without installing things on the real host. That would avoid a lot of hassles and conflicts, and allows easy revisiting of old development environments.
This seems like an obvious thing that should be readily available, just like the standard images that many projects provide.
As I am just looking to evaluate things, I'm not that picky about tools. A development language/framework (Node.js), a database (MySQL), and web server capability (anything). If it's PostgreSQL, MongoDB, whatever. I just don't want to spend days wrestling with setting things up, before I actually get to start evaluating the platform.
I tried asking this over on DevOps a few days ago. All I got was one snarky and unhelpful comment, which has since been deleted.
I have tried following a bunch of different tutorials around the web and answers given here, but they all fail, and I really don't want to get sidetracked debugging them.
It seems like this would be a common template for starting many projects, regardless of complexity or expertise. So, I'm really surprised I can't find it. It also seems like a good way to lure in new users, which should incentivize project maintainers to have these.
The company I work for offers a wide array of services, a lot of which involved compiled application development. A small portion of development is web software using interpreted languages like PHP, where any changes are instant.
The company has also invested in CloudForms and would like it to be used for all development environments where possible, but I am struggling to find a development pattern that works for a PHP/JS application, without adding overhead to the development process.
The main thing I can't get my head around (and can find nothing online for) is how one would manage to sync a local codebase to the remote dev server. This is simple with locally hosted VM solutions like Vagrant. A developer can just change a file and refresh the local website.
Does anyone know of a pattern for this, or CloudForms-specific tool that would support live and instant code sync? The only options we've managed to come up with is an Rsync script (we found it to be unreliable) and doing commits and pulls via GIT (terrible overhead and it means we have to commit every single change just to see if solves a given issue).
Are we better off sticking with local VM development for this sort of software if it works?
I am a rails backend developer and I am now working in a team with an HTML coder and I have some problems with information exchange.
I want him to generate all the HTML templates (haml, erb, whatever) and css files. But he has actually no clue on how to install ruby (and rails).
So, we are working now in this ugly workcycle when he puts all html's and css's in public, test them, and then I (myself) move them to correct place.
Is there a tool (for HTML codes) that mimics Rails rendering part so he will run this tool, which must be easy, and when the server starts, he can put all the templates to app/ and test them?
I see this as a small easy installable subset of rails, that only deal with page rendering.
If your coder still doesn't know how to install ruby or how to configure stuff for works , then I can say this is quite problematic . You either can try any cloud based IDE . Or , tools like git to get only raw stuff.
But , you also can look for someone who in minimum way will try to make the whole process possible by learning and installing ruby in their pc .
I had a similiar problem where a copywriter needed to play with the html and we ended up using Cloud9.
Cloud9 is a collaborative IDE in the cloud, IMHO It's pretty decent for small scale projects and can really get the job done.
I simply installed rails once and ran a local dev server and she did all the modifications and watced the preview.
Another option is to create a vagrant environment and preisntall rails there. This means the HTML coder would have to install a VM on his machine and run the vagrant there.
I have this dilemma where I spend most of my development time making minor css/html changes in a large project, but spend 30+ seconds waiting for my build tool (grunt) to implement the changes, load all of the front-end project resources (bootstrap, etc), and then reload then reload the page.
My question is about the development environments others set up to ONLY make html/css changes. Do you use codepen and copy the project files over after you create your finished project? Do you just run the front-end from your machine and load it in a web-browser? Am I missing something entirely in my development process?
I usually do small changes on element inspect from chrome then implement it. After a lot of changes I reload.
Also, there are some IDE that supports live changes like JetBrains
Just build and test the frontend using placeholders for your server generated data. When you are ready, incorporate the back end.
What are the options for having a simple blog, content management system that will deploy the full site as static html over FTP/SFTP and any blog API?
I am aware of Thingamablog but it hasn't been updated in more than a year so i guess is dead now. What are my alternatives that must export at least static HTML to a FTP server?
It would be nice if the app would have some visual gui to enter the blog post and could run from a USB stick.
I don't know that Thingamablog is dead just because it hasn't been updated in a year. Lack of recent updates doesn't necessarily mean the project is dead, it just may mean that it has achieved it's goals and has nothing more to add. Does Thingamablog do what you need?
How about TiddlyWiki. Not a blog or CMS, but it seems to be the kind of thing you need.
Today I came across this tool: Zeta producer. They have a free and a pay version.
Second the motion for CityDesk. You could probably run your blog on the free version (up to 50 "assets" - files, pages, images, etc.), and publishes static HTML to servers via FTP as its specialty. It's trivial to add updates; re-publish process does a differential between your new version and the one that's on the server, and only makes necessary changes.
Examples abound - just google for "*.cty" files.
Here's a CityDesk site I help run:
http://bv-embs-chapter.com
Hope this helps.
Thingamablog is active again. 1.5 will be released soon, currently 1.5veta5 is the latest. Looks good for what you need.
Paul.
You could use the MoWeS Portable: The Modular Web Server.
http://www.chsoftware.net/en/useware/mowes/mowes.htm
It lets you pick and choose a number of static and dynamic services to run on top of a web server straight off the USB drive or a virtual drive.
I run a Wiki off a virtual drive using Mowes at work and at home, i run a personal blog from my usb stick.
Its verrry easy to configure and powerful enough to be productive.
Edit: Heres a link to help you get started with it:
http://www.mediawiki.org/wiki/Manual:Installing_on_WOS_Portable_(Windows)
In the download section, you can select what packages you want to install. This is where you can select what CMS/Blog softwares you want to include.