When I would like to test live my code : I push my dev files from my dev folder to beanstalkapp
beanstalkapp keep a version of all my work help my colleagues to review the code.
beanstalkapp is set up to automatically deploy my dev file to a ftp server.
I use ovh and a public dev folder http://thomasdt.com/myproject_dev
This is a php-sql project so :
I maintain a duplicate of the public database
If you are browsing the application through :
http://thomasdt.com/myproject, the php files are pointing to the live database
http://thomasdt.com/myproject_dev, the php files are pointing to the test database
When I would like to push the dev to the live site. I commit my files with the keyword: [deploy: production] and the files are also pushed to the production ftp server.
If I need to alter the sql database structure, I do it in a sql.php file rather than in phpmyadmin. This sql.php file is automatically triggered (like a web hook) by beanstalkapp just before deploying the file to the development and production server.
Things I could improve
On windows, I am pushing files to git with Git Bash and this is not optimal. I could find a better IDE with integrated git.
Hi, In the last year, I have been developing a CRM for some very good friends that own a salsa school and a fitness club in Lyon, France. The software fits perfectly their needs. After some moments of hesitation, I have decided to write a public version so that any interested school can give it a try.
Store all your customers data
Manage your classes and attendees
Send group emails
Fully billing system to send your customers their bills
Manage cards with point system for non-regular customers
Get customers birthday reminders
Get bad-payers list in your mailbox every morning
Take customer pictures directly from Smartphones and tablets into the CRM
It helps the note taker to remind himself about important facts discussed in a meeting or during a presentation.
You can make them way more useful if you convert them into organized knowledge.
Under organized knowledge I mean a document recorded in the company database.
A good practise would be to convert every items of your freshly-taken notes into :
An assigned action with due date
An update of documentation like a specification or a handbook
An update in the project decision log
An update in the risk (or opportunity) register
A short communication to colleagues
A planning update
A change in the software
Whatever you want but something else than a hand written document than no one will use
Don’t wait too long to do this. Try do do it live or at least within one week period.
Doing it quickly after the meeting prevents :
People to wait too long for your feedbacks
Having to convert tons of notes at once.
This seems obvious but sometimes it is useful to recall obviousness.
Voici mon dernier petit développement. Un système de contrôle d’accès par badge pour salle de sport ou salle de danse.
Chaque client à une carte associée à son profil. Chaque fois que le client veut rentrer dans l’école, il passe sa carte devant un système autonome. Le système doit juste être branché à l’électricité. Le système dialogue avec un serveur qui renvoie l’image du client et toutes les informations associées à son profil. Le système est déjà couplé avec le CRM que j’ai développé mais vous pouvez aussi le coupler avec votre propre système de gestion client.
Prochaines étapes :
Installation dans une école pilote
Si vous êtes intéressé, je le vends. Pour les tarifs : firstname.lastname@example.org
As I go on with the development of the Rocket.pm and especially the Document Managing System (DMS) function, I came across the definition of a key role in knowledge management : expert knowledge manager.
Let’s assume that I have a document database in which documents cover different fields of expertise (like steel materials and ceramic material). I can define one (or more) colleague(s) as an expert in a given field; For example, Bruce is defined in the system as an expert in ceramic materials.
The document creator (let’s say a colleague from the ceramic material engineer department) has not been able to fill in every form field (or attributes) when submitting the document. I really don’t want to make all field mandatory because it may make the document creator reluctant to add its document to the database. That is why, the system let him submit its document with an incomplete form and as a consequence the entry in the database has some missing information.
Here comes the Expert Knowledge Manager in action.
The DMS will regularly ask the right Expert Knowledge Manager to fill in the blank fields. If a document cover the ceramic material subject then Bruce will be asked to improve the database entry. In other words, the expert knowledge manager make sure that all documents in his field of expertise are well documented and can be found in the database.
The philosophy behind is always the same : a DMS will work only if all documents are properly defined and all attributes are correct.