@treaz Since we already published 2.7-RC, I think we can publish 2.7 docs anytime. Maybe the process should be below:
- Create 2.7 branch, then create 2.7 directory and copy 2.6 docs to 2.7 directory on 2.7 branch
- Update 2.7 docs on 2.7 branch, then create a pull request
- Merge into master, then publish the website
@treaz I tried Huge v0.36.1, but it didn't work too. Hugo v19.0 is used for building the website on TravisCI: https://github.com/scalatra/scalatra-docbuild/blob/dcb75b67d83d1a4498c837c1242aa89dbef9ccf6/.travis.yml#L17
It's too old. We might have to upgrade Huge.
(i.e. not an RC)
Hmm, I deployed Scalatra website after merging scalatra/scalatra-website#202, then many existing files were deleted and the doc site is now almost unavailable. I don't have time to fix it today. Will check on next weekend or later :bow:
@takezoe
Hmm, I deployed Scalatra website after merging scalatra/scalatra-website#202, then many existing files were deleted and the doc site is now almost unavailable. I don't have time to fix it today. Will check on next weekend or later :bow:
that's my bad... I tried to use shortcodes somewhere where it was not allowed and I didn't test locally. Fix: scalatra/scalatra-website#205
@treaz Thanks! We use this project (https://github.com/scalatra/scalatra-docbuild) for deploying the website. Deployment process runs on TravisCI. I will invite you to Scalatra organization so that you can get permission to write to GitHub repos and manage TravisCI jobs.
Deploy job is: https://travis-ci.org/scalatra/scalatra-docbuild
We need to run the website deployment by running the above Travis job by hand. Now it's running after merging scalatra/scalatra-website#205
The website got back. Thanks @treaz! http://scalatra.org/
I wish it wouldn't get broken in the first place. I've created an issue to check if there's anything that can be done about this (some tests&rollback)
@takezoe the scalatra website is currently running on HTTP. Switching to https is just clicking a checkbox, but only an admin can do it. https://help.github.com/en/github/working-with-github-pages/securing-your-github-pages-site-with-https
Thanks
@msilvestre I don't want to be unwelcoming, but when I read your question, I'm thinking "what does this have to do with scalatra?". I'll help out this time, so I'm curious if you already tried to exclude the jetty library from hadoop-common (libraryDependencies += "foo" % "bar" % "0.7.0" exclude("org.baz", "bam") ).
i am using sbt test
Scalatra 2.7.0 is now available!
https://scalatra.org/2020/03/01/2020-03-01-scalatra-2-7-0-released.html
https://scalatra.org/2020/03/01/2020-03-01-scalatra-2-7-0-released.html
Hi everyone!
I'm having trouble adding the swagger example field introduced in scalatra 2.7.0
For example
does not add
to the generated swagger.json document
I see here scalatra/scalatra@b17bc7e that the example was removed from the tests, so I guess I'm not using the correct way to add example value to my Swagger API.
Do you know what's the proper way?
Thank you.
I'm having trouble adding the swagger example field introduced in scalatra 2.7.0
For example
parameters pathParam[String]("pathPath").description("a description").example("John Doe")does not add
"example": "John Doe"to the generated swagger.json document
I see here scalatra/scalatra@b17bc7e that the example was removed from the tests, so I guess I'm not using the correct way to add example value to my Swagger API.
Do you know what's the proper way?
Thank you.
I would be sad to see Scalatra depend on http4s, as would lead to FS2 and Cats dependencies. A general open-source library, like Scalatra, should really try to avoid this, particularly on rapidly evolving libraries, as the chance of incompatible dependencies from other projects is almost unavoidable.
I can see that this approach has been abandoned, but for other reasons.
I can see that this approach has been abandoned, but for other reasons.
@nilskp Actually, a creator of Scalatra was a creator of http4s. So, Scalatra and http4s had a connection. One good point of http4s was that it supports Servlet based backend not only Netty based non-blocking I/O backend. Anyway, I think migration to http4s would never happen on Scalatra due to the lack of our development resources.
sbt on a fresh scalatra app, instead of binding to a normal network ( localhost:8000 ) it binds to a unix socket. How would I change the port binding?
I found a video of the presentation about Scalatra + Slick + ZIO at ScalaUA conference!
https://www.youtube.com/watch?v=mAQAxh-K14g
https://www.youtube.com/watch?v=mAQAxh-K14g
