schultyy / datjournaal_v1 Goto Github PK

It sometimes shows "sign in" instead of "dat Journaal".

On a bigger screen it should be possible to show a bigger preview of the image to be uploaded

As an logged in user I would like to be able to see statistics to find out, which posts are popular.
In order to accomplish that for each request a log entry in the database shall be made. This contains the IP Address (maybe a unique id or hash of the address), the time and what was requested.

When datjournaal gets deployed the very first time, this happens:

Error: Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.
r()
application-2896a18bc1ae10ffd71fb461108cc17b.js:19
N<.createRouterObjects()
application-2896a18bc1ae10ffd71fb461108cc17b.js:19
bound ()
self-hosted
N<.componentWillMount()
application-2896a18bc1ae10ffd71fb461108cc17b.js:19
v.performInitialMount()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
v.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
a<.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
v.performInitialMount()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
v.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
a<.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
v.performInitialMount()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
v.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
a<.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
v.performInitialMount()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
v.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:17
a<.mountComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
i()
application-2896a18bc1ae10ffd71fb461108cc17b.js:18
o<.perform()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
c()
application-2896a18bc1ae10ffd71fb461108cc17b.js:18
o<.perform()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
p.batchedUpdates()
application-2896a18bc1ae10ffd71fb461108cc17b.js:18
a()
application-2896a18bc1ae10ffd71fb461108cc17b.js:2
B._renderNewRootComponent()
application-2896a18bc1ae10ffd71fb461108cc17b.js:18
B._renderSubtreeIntoContainer()
application-2896a18bc1ae10ffd71fb461108cc17b.js:19
B.render()
application-2896a18bc1ae10ffd71fb461108cc17b.js:19
<anonymous>
application-2896a18bc1ae10ffd71fb461108cc17b.js:1
t()
application-2896a18bc1ae10ffd71fb461108cc17b.js:1
<anonymous>
application-2896a18bc1ae10ffd71fb461108cc17b.js:1
t()
application-2896a18bc1ae10ffd71fb461108cc17b.js:1
<anonymous>
application-2896a18bc1ae10ffd71fb461108cc17b.js:1
<anonymous>
application-2896a18bc1ae10ffd71fb461108cc17b.js:1
application-2896a18bc1ae10ffd71fb461108cc17b.js:19:9725

The post's description should be optional. Only the image itself is required.

Right now none of the images are visible in production because of a malformed image url:

<img src="//var/apps/external/uploads/thumb-a7f8dc92-6c0a-4472-b5f7-f5faa323dd52.jpg.png?v=63643351435">

This happens right now because the Arc image uploader has a different storage_path configured. The problem though is that this storage path is used for both storing the image but also for determining the url.

As a user I create a new post and want to decide whether I want to share it on Twitter. The posts/new view needs to have a checkmark for that.
A tweet is published with the following things:

• The description (if present)
• A link to that particular post (we need permalinks for every post then)
• Maybe an image preview (need to check if that's possible /w Twitter)

As a user I create a post with text with 399 chars saving fails with:

    ** (Postgrex.Error) ERROR (string_data_right_truncation): value too long for type character varying(255)

It should be possible to create posts with texts > 255 chars.

As a user I would like to be able to group certain posts by applying hashtags. A hashtag is denoted with a leading '#' and a word.
When a visitor clicks on the hashtag, they get see all posts which have that certain hashtag applied.

Right now the user can pick any file they want for upload. Instead they only should be allowed to upload images only.

Through OpenGraph iMessage for example is able to fetch preview images http://ogp.me/ and more meta information which is then displayed below the link.
This also might be interesting for Twitter as well.

As a user I want to be able to attach the place where I took a picture. This needs to be stored and shown when all pictures are rendered.

In development mode it's okay that the Phoenix application serves uploaded files as well. But in a production environment this should be done by another web server (like NGINX).

When I am not logged in, yet I can access /posts/new. This should not be possible. Instead I should get redirected to /.

When I sign out, all previous state needs to be invalidated like reloading all posts etc.

When I create a new post and try to upload an image with a size > 10MB I receive an HTTP 413. Right now the application is not able to handle that and the form's frozen afterwards.

There needs to be some official information about copyright and a small about page with an imprint.

As a user I would like to be able to import posts and likes from Instagram.

Right now posts do not have a user assigned. It is important that every post has a reference to the user how uploaded it.

Right now the PostController receives a file upload and metadata which are not JSON encoded. They're sent as Form Data, but the Router clearly specifies it accepts json.
This solution works but is not great.
Maybe it makes sense to handle that specific part via a different pipeline.

Every post should have a small menu which offers a couple of entries:

• detail view
• hide (only if user is logged in)

When I post an image which has a filesize >= 10MB it won't be accepted. Right now the error gets returned as HTML but should return JSON instead so it can be parsed without problems.

Dominik referred to sputnic:

dominik [14:18]
frag doch mal sputnic, die machen unsere t-shirts

dominik [14:31]
[email protected]

[14:31]
schoene gruesse von mir

This needs to be done before #11 and #13

Right now, all posts are rendered as a list when the user visits the root path. In order to be able to link to a specific post it should also be possible to show one post separately.

The URL should look like this: /posts/:id.

When there's more posts in the database, it's not feasible to load all of them at once. Therefore there should be some pagination in place which enables the user to load more images page by page.

As a user I want to be able to configure social media accounts:

• Twitter
• Facebook

In a production environment it should not be possible for users to use the sign up form. All users in the system should be created via the db console instead.

When I create a new post without image and description it produces an argument error on the server. This probably happens because it tries to create a custom filename before validation took place.

When the JavaScript components are compiled with NODE_ENV=production the logs should not contain debug output.

See this article:

https://medium.com/@jsaito/making-a-case-for-letter-case-19d09f653c98#.f6bdljnk8

As a logged in user I want to be able to hide certain images. A hidden image is not shown to a regular visitor but can still be seen by a logged in user.

Check if it makes sense to render a preview of the image to be uploaded.

The location for the uploads folder should be configurable. In development it's fine to have it at uploads/ but in production it maybe makes sense to host it in a different place.

Need to find out what's necessary to provide in order to get a good experience when the user adds it to their homescreen

When datjournaal is run in production, logging is not on apparently. This makes it very hard to see what's going wrong in case of failure.

I believe this is the error which happens mostly after a fresh deployment. When the app gets deployed again the error is gone.

Refused to execute script from 'http://localhost:4000/js/application.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.

Set the alt text = description for each image.

Right now a post is accessible by its id:

/posts/54

Instead of exposing the database's primary key a post should be accessible by a slug.

When I am logged in and view a post via the URL /posts/:id on a small screen (limited height) the footer overlaps parts of the image and description. To prevent this a scrollbar should be shown.

Given the case I'm on holiday and I create multiple posts during that time. I then would like to be able to group these posts in the story "Holiday".

It needs to be figured out how to deploy the application to the production server.

All posts should be available via RSS feed. The RSS feed should contain the latest 30 posts.

The users can subscribe to it via a link from the main page.

I pick this image
and it fails with the following error:

TypeError: Argument 1 of FormData.constructor is not an object.

Right now the server returns urls which look like this:

uploads/thumb-foo.jpg

Instead it should URLs like:

/uploads/thumb-foo.jpg

When logging stats it also should be logged if the user is logged in or not.

When a user creates a new post, a loading indicator should be shown for the time the upload is in progress. During that time the upload interface should be disabled.

When datjournaal is run in production mode, it produces the following right now:

"Warning: It looks like you're using a minified copy of the development build of React. When deploying React apps to production, make sure to use the production build which skips development warnings and is faster. See https://fb.me/react-minification for more details."

You are currently using minified code outside of NODE_ENV === 'production'. This means that you are running a slower development build of Redux. You can use loose-envify (https://github.com/zertosh/loose-envify) for browserify or DefinePlugin for webpack (http://stackoverflow.com/questions/30030031) to ensure you have the correct code for your production build.

As a logged in user I can only hide/show images I created by myself. It is not possible to do that for other people's images.

As a logged in user I want to be able to browse stats collected by the application. I want to see how many people viewed the page today and over the last 30 days.

For the start it is sufficient to just show text. In the future it makes sense to show them in a simple line diagram.

As a logged in user I would like to see how many users visited the page

• Today
• Yesterday
• The last week