Recently Browsing 0 members
No registered users viewing this page.
we started our first Processwire driven project in my new company and for the first time, I was working on one site with more than 2 colleagues on the same site.
It didn't take long for us to stumble across some problems when multiple developers work at the same time, conflicts with updating the database on vagrant machines, like duplicate entries for page IDs, errors when setting up fields and stuff like this. We ended up working on a dedicated database server, that we linked to our vagrant machines and most of the problems were gone, but the performance of this constellation is really bad compared to our first approach with database running on vagrant machines.
I already tried to find a solution in the forums but I couldn't find anyone with problems like this.
So I was wondering: how do you manage projects with multiple developers on vagrant machines in a git-based workflow?
The Module Blog for ProcessWire replicates and extends the popular Blog Profile.
Blog is now in version 2.
Please read the README in the Github link below in its entirety before using this module
As of 20 December 2017 ProcessWire versions earlier than 3.x are not supported
Blog Documentation is here (Work in Progress!)
See this post for new features in version 2 or the readme in GitHub.
To upgrade from version 1, see these instructions.
Most of the text below refers to Blog version 1 (left here for posterity).
Blog version 1 consists of two modules:
ProcessBlog: Manage Blog in the backend/Admin.
MarkupBlog: Display Blog in the frontend.
Being a module, Blog can be installed in both fresh and existing sites. Note, however, that presently, ProcessBlog is not compatible with existing installs of the Blog Profile. This is because of various structural and naming differences in respect of Fields, Templates, Template Files and Pages. If there is demand for such compatibility, I will code a separate version for managing Blog Profile installs.
In order to use the 'Recent Tweets Widget', you will need to separately install and setup the module 'MarkupTwitterFeed'.
Please read the README in the Github link below in its entirety before using this module (especially the bit about the Pages, etc. created by the module).
I'll appreciate Beta testers, thanks! Stable release works fine.
Modules Directory: http://modules.processwire.com/modules/process-blog/
You can also install from right within your ProcessWire install.
Screenshots (Blog version 1)
The Alpha Testers and 'Critics'
I'm a System Administrator responsible for DevOps in our Company. We're trying PW in a single client project atm and experience some glitches with DevOps-/Workflow.
We have a small team of developers that need to work with the same code base. They all need to be able to develop locally and deploy to a preview/staging environment.
Our Toolstack contains git for versioning, chef/vagrant or docker for local development/testing and Jenkins for building assets and automatic deployment to the staging-site.
There's several challenges / glitches in this process that makes me think that ProcessWire hadn't been developed for a use case like ours and is much more intended to be used by single developers that work right on the production system.
Can you advise me on a suitable workflow?
There's problems with the assets/files dir that must be shared between the staging website and local environments of our developers.
We're right now working with symlinks on the staging system that helps to preserve the direcory when deploying from the master branch. but now we tend to use nfs-shares so devs can collaborate with a shared directory.
The local docker containers can use the same target (the nfs) from inside the containers. But is that the way it needs to be done? Really?
There's so much work that needs to be done to fit ProcessWire in a DevOps Workflow that we tend to decide to switch to another CMS.
Any suggestions or hints that i might have missed. Am I wrong or is PW really not meant to be used this way. I
Hello All ... I just added a new Site Profile ...
It is important that you use the latest version that supports the new Fields => Fieldset in Tab , Fieldset ( Page ) for this time it is version 3.0.83 DEV
A simple profile for quick start new Page ... There are several pages like About Us, Blog, Portfolio, Contact Page ...
The profile is not based on any framework, I just used some css, flexbox, grid, font awesome, and added a simple FlexBox Grid called GRIDLEX ...
CAN DOWNLOAD FROM THIS LINK:
In addition, I added 2 great modules:
I'm new in Processwire CMS.
and when i create my first website on it i notice it's very slowly.
i tried use AIOM module to resolve the problem but when i try using this
the website doesn't open it's appear Blank page
can anybody help me, and tell me where the problem?