Adding Images to Posts and Subweddits using Storage

I've left this part of the project until the posts and subweddits were completed to avoid over-complicating things, as I know its a case of a simple migration and a bit of fiddling in the controller from this point.

Both subweddits and posts will have some sort of file upload, in the form of an image. Subweddits will have their logo, which is mandatory, and posts can have an optional image upload.

We must first make a migration to add_logo_to_subweddit and add_img_to_post. Besides the names of the fields, the migration looks the same.



These are both the frontend and backend of the new file upload.



These files could be anything, so require both clientside and serverside validation, but these will be attempted later on, I'll focus on the functionality first.

Once the data is passed to the controller, there must be a way to save the data, for that we need to import 'Storage' [do full path], and set the path of the image to the logo/img/field. so save being confused, I'm going to organise my laravel storage directory a bit, so that all data is kept in a folder of the subweddits name, with post images being kept in a further subfolder named 'posts'.

For these to be accessable, I will create a route to the image or logo under w/{subweddit}/{post}/img and w/{subweddit}/logo respectively, where they are publicly available.



When calling these, we make a request to the routes containing the logo and the image, which will pull the image and display it on the blade.


Comments

Post a Comment

Popular posts from this blog

Validation

Image
validation, both serverside and clientside, is essential  for a satisfactory user experience, and for security.  This application makes use of several forms, so it is important that the site be completely tamper-proof. Thankfully, Laravel takes helps the cause, with the @csrf tag, which prevents csrf attacks, or cross-site request forgery. (explain this). validation on the registration is handled largely by the livewire auth package, the only tweak made is validation for the username, which was covered in the auth blog post. which leaves 5 forms to validate: create subweddit create post edit post create comment create reply Client side, all of the validation can be handled by laravel's @error directive, which will quickly determine if there is a validation error in an attribute. The message can be displayed by calling the array $errors. With our Bulma framework, we can make things look a little prettier for the user by changing the form border to red and displaying the red err...
Read more

Views and Policies

Image
Although maximum functionality is achieved by being a logged in user, it is important to think of guest users browsing the site. Baring that in mind lets run through the abilities guests and users: Guest: Home feed showing most recent posts from all subweddits view subweddit and contents view post and comments sign up User: Log in Personalised home feed Create subweddit Follow Subweddit Create Post Post comment/reply to preface: guest and user views could have been achieved in a cleaner way by creating seperate routes in web.php and stating if the user is logged in, redirect to 'logged-in' views, or otherwise 'guest' views. As my AWS instance is running on micro I chose to slim my application down so as not to overload my tiny server. Thusly, I opted for utilising @auth and @guest in the blade file. Not very clean, but effective and 'cost' efficient Starting with the index page: if the page is viewed by a guest, then display all posts from all subweddits, filter...
Read more

Creating a login system with Jetstream & Livewire

Image
For this project I will be using Jetstream and Livewire to create a killer login system. This process couldn't be simpler, only requiring 3 lines of code. composer require laravel/jetstream php artisan jetstream:install livewire npm install && npm run dev and voila! a working authentication system! but let's make some personal tweaks.. Perfect... When signing up to Reddit.com, you are asked for your name AND  username, which is not available out the box with livewire, so we must adapt! Firstly, I added a new field in the Livewire's register.blade.php form to take in 'username'. The issue now being that Reddit does not allow spaces in their usernames. A quick bit of validation in Fortify's 'CreateNewUser' action using the argument 'alpha_dash' means that usernames may be alpha-numeric and also contain dashes and underscores. And make sure to persist these changes below! At this point, the form appeared to be displaying correctly, and valid...
Read more