ledermann / docker-vue

Frontend for DockerRails, built with Vue.js

DockerVue

Single-page application (SPA) built with Vue.js. It's is a very simple kind of CMS (content management system) allowing to manage posts (articles) with images.

This is the frontend only. The backend is a separate project called DockerRails, created with Ruby on Rails and responding as an JSON API.

Tools used

• Project scaffolding with Vue Cli
• Routing with Vue Router
• State management for authentication with Vuex
• Package building with Webpack and Yarn
• Styling with Bulma, Buefy and FontAwesome
• API calls with Axios
• Deployment with Nginx and Docker

Features

• User authentication using JSON Web Token (JWT)
• Infinitive scrolling using Vue-infinite-loading
• Auto refresh via ActionCable
• Searching with Buefy Autocomplete
• Content editing with the WYSIWYG editor Pell
• Image gallery with Silentbox
• Uploading images directly to Amazon S3 (presigned by the backend)

Demo

There is a live demo at https://docker-vue.ledermann.dev/

Development

First, make sure to get the backend up and running: https://github.com/ledermann/docker-rails

Make sure the backend is available locally, for example at https://docker-rails.test. Then:

git clone [email protected]:ledermann/docker-vue.git
cd docker-vue
cp .env.local.example .env.local
yarn install
yarn serve

Why?

I built this application to learn Vue.js.

docker-vue's Issues

Can't select article

Hi,

When i start type something on search box, if I click with mouse on the article I want to read anything happens because the value is undefined:

Typing:
https://docker-rails.georg-ledermann.de/api/v1/posts?q=carva

Click with mouse:
https://docker-rails.georg-ledermann.de/api/v1/posts?q=undefined

How is it possible to fix?

Thanks

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.