Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pagination for the CfPs #3

Open
heiglandreas opened this issue Mar 3, 2016 · 6 comments
Open

Add pagination for the CfPs #3

heiglandreas opened this issue Mar 3, 2016 · 6 comments

Comments

@heiglandreas
Copy link
Member

Currently all CfPs are output when the list is called.

There should be a paginated output, at least when JSON or HTML is output. I'm not so sure it makes that much sense when exporting a calendar or an RSS feed....

@czmole
Copy link

czmole commented Oct 3, 2018

I can check on this

@czmole
Copy link

czmole commented Oct 14, 2018

hi @heiglandreas sorry, a question might be dumb :) is there any data migration I could use or how can I get some data for testing? Thank you.

@heiglandreas
Copy link
Member Author

No dumb questions 😉

Have you had a look at https://github.com/joindin/joindin-vm/blob/master/README.md? If you follow thst it should also seed the database. Or are you setting it up on your local machine? Then you migvt need to run the scripts/patchdb.sh shellscript to seed the database...

@czmole
Copy link

czmole commented Oct 14, 2018

No, I haven't checked on that :(

I thought the callingallpapers-api can be run independently as the contributing guidelines do not mention the connection between. the VM readme and this one.

I am running windows. I have the VM for joindin configured and running.

Do I have to clone this repo inside the same folder with joindin-vm next to joindin-api , joinedin-web2 and joinedin-legacy folders?

@heiglandreas
Copy link
Member Author

You can run the API independently from the others. But it's easier to run it like that 😉

The API folder needs to be a sub-folder of the VM-folder like this:

joindin-vm/joindin-api

You don't necessarily need the web2 or legacy-folder if you are only doing API-stuff.

So I'd clone the VM and then move the API-folder into it and then call vagrant up.
As long as the API-folder is named as expected (joindin-api) everything should work. 😉

@czmole
Copy link

czmole commented Oct 15, 2018

Thank you, I will try it that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants