-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
I can check on this |
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. |
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... |
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? |
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. |
Thank you, I will try it that way. |
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....
The text was updated successfully, but these errors were encountered: