-
Notifications
You must be signed in to change notification settings - Fork 159
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
请问 静态资源在哪 我没找到 #1
Comments
好的 谢谢。我看到了。我研究下前端框架
「fossi <[email protected]>」在 2019年3月28日 週四,22:07 寫道:
… https://github.com/sunweiguo/snailmall-front readme的最后
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AlTc5k7Dq0R_gYiBNj2sr0eXsg6gfid9ks5vbMytgaJpZM4cNKWx>
.
|
最近在学习你的项目,请问你有没遇到token问题,就是cookie只能获取到jsessionid不能获取到自定义的token。虽然作为入门者,还是推荐使用pom中设置环境profiles参数,在yml中使用active: ‘@spring.profiles.active@’方式进行环境切换,也方便打包。 |
pom中:
yml中:
|
没有遇到哎
「ke00ke <[email protected]>」在 2019年4月27日 週六,上午1:58 寫道:
… pom中:
src/main/java
**/*.xml
src/main/resources
<include>**/*.*</include>
</includes>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
</plugin>
</plugins>
</build>
<properties>
<resource.delimiter>@</resource.delimiter>
</properties>
<profiles>
<profile>
<id>dev</id>
<properties>
<spring.profiles.active>dev</spring.profiles.active>
</properties>
</profile>
<profile>
<id>test</id>
<properties>
<spring.profiles.active>test</spring.profiles.active>
</properties>
</profile>
</profiles>
yml中:
spring:
profiles:
active: ***@***.***@'
eureka:
client:
service-url:
defaultZone: http://192.168.1.104:8084/eureka
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJKNZZWTYZRKE75E6VZ2PXDPSM7DHANCNFSM4HBUUWYQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: