Find a professional PHP developer in Melbourne

Web Developer for creating UI in linux OS from php application with knowledge of apache Must be experienced/skilled in: *PHP *linux *apache skills in following helpful but not necessary *MYSQL/MariaDB *Mac OS Job is negotiable in rate and time Must come in to office for at least initial discussions

Programme is about 80% complete so just needs some tweaking and finishing touches plus a few other changes. Given we are currently in lockdown in Melbourne this job would ideally suit someone in Melbourne. See skill sets and detailed brief below. Online Property Tracker Database The backend database is MongoDB. Shell Version: 4.2.8 Project Stack Laravel 6+ Project stack is split between a backend using Laravel API and client side views via Vuetify as a replacement for Laravel Blade templates. The application is a single page web app. For more information regarding Laravel and Vuetify, please visit the links below. Laravel: ​https://laravel.com Vuetify: ​https://vuetifyjs.com/en/ Authentication JSON Web Tokens (JWT) combined with Laravel’s inbuilt authentication. Project Overview Environment File The environment file (.env) contains the variables that are used within the application. To be able to reference variables within Vue and PHP, they must be prefixed with “MIX_”. The developer may wish to setup additional variables in this file to override settings referenced in other files such as database.php etc. Configuration This project follows the structure of a typical Laravel project. Default values for MongoDB database settings are already set in database.php. Developers familiar with Laravel will already know that any third party packages are referenced by Laravel in the composer.json file. If additional packages are needed, the developer should consult instructions as indicated by the author. Backend All server side logic uses middleware to protect the endpoints from unauthorized requests. Requests from the server to the database are done via Eloquent queries. More information can be found in Laravel’s documentation. A typical flow: ● A user signs in with a username and password. ● The server generates a token and sends it back to the client ● The client then saves the token and appends it to the Authorization header for all subsequent requests. Structure of the backend follows the typical Laravel design of having Controllers, Models, and Views. The exception here is views. Laravel is not used to render views besides emails as the main purpose for the project is to provide an API. Client Side This Laravel project is setup to use Vuetify which is a flavour of VueJS. All page routing is handled by Vue Router and not Laravel. This allows the application to take all the benefits of a single page application. The client side design follows a typical VueJS structure. Vuex is used for most API calls and state management for the app. As with any javascript front end that uses NPM, all third party dependencies are listed in the package.json file. Scheduler Laravel provides a very unique and intuitive way to manage Cron Tasks. The Kernel.php file of the Console folder contains a task that is scheduled to run in the morning. For additional usage and for how to schedule cron tasks, please visit the Laravel website. GMAIL API This project does not use the standard Mail sender as there were issues such as incompatibility with the Google SDK at the time of development. A work around was to manually render a PHP Blade template, inject required variables, and then use the Gmail SDK to send out the mail. The template is encoded in a format compliant with Gmail. Required Skills This project requires a developer with strong programming skills and strong understanding of object oriented design. Although VueJS makes observables and streams much easier to understand than other frameworks, it’s important that the developer has a strong understanding of reactive programming. The developer needs to be familiar and confident in configuring linux servers as they may need to install or maintain libraries. Version Control It is extremely important that the developer uses version control. Most developers have their own repositories that they pull and push to during the development phase. I have removed reference to my own repository and added a new repository in CPanel in the property tracker account. It is a fresh repository with no reference to any personal developer details. You should only let trusted users have access to this. Alternatively, you can let developers use their own repositories. Most will anyway. I have created a master branch in your new repo. Developers of course will create their own development branches to work off as is the case that I did with my own repository. Summary of Skills / Experience ● VueJS ○ Vuex ○ Vue Router ○ Vuetify ● Laravel 6 + ○ Eloquent ○ Migrations ● MongoDB ● Web API design ● Authentication using JWT ● Server deployments ● Familiarity with Unix shell commands. ● Version control using GIT. ● Ability to problem solve and troubleshoot Laravel. ○ Common errors when first working with Laravel ■ File permissions, environment files not set, etc. All the above are important. A developer that knows their way around VueJS and Laravel will be able to assist. Screenshot of DNS Settings

I need to arrange a discussion to fix up a php web application.