Style of error pages is ugly. At least top fix css should be applied, say, below navigation bar.

We should add cookie usage notification in login page.
If browser stop using cookies, this site would not work.
Small fix, i think.

期 is not shown now.
Change admin-user and profile file. The user should have user.class_year not user.class_year_id.

In this case, we have to omit the data.
Programically we do not consider this kind of case.
Such a case should be omitted by bare hand.

Because BCrypt style of encryption is already running.
So that our authentification system should use also same encryption system.
Before deciding authentification frame work, you should check up whether encryption really solved or not.

Bugs are the following.

• class_year for files should be included.
• learn_term should be replaced with "pre" or "post" not "a" or "b".

In the home page, the font of the title can not be changed with font-family.
The cause of this problem can not be solved by myself.
Maybe SASS setting is not the cause. font-face? also can not be applied.

Since my computer does not have many fonts, I do not certainly say this problem exist universally.

Because the structures of database will change much, re-enter the database information to new information.
The candidates tools to achieve this will be sqlite3 for python.

Want https settings.

If the file is given, upload and download function should be prepared.
The original hokuinet uses the direct access and token authorization,
however, if we correctly set the path to the file, we can give (user can fetch) the files without file token system. Access token is enough, i think.

• Q1. ドメインは元のものを再利用するのですか？
  Ans. いいえ，新しく取得することにします．旧versionへのリンクを貼って遷移出来るようにしたいからです．
• Q2. DBは元のものを取り込むのですか？
  Ans. はい，取り込みます．データベースの構造を同じにしてしまえば，そのまんま流用することが出来ます．ちなみにDBはsqliteです．
• Q3. gmailアカウントは新規のものを取得しますか？
  Ans. はい，取得します．ただ，gmailが適切かどうかは微妙です．複数人で共有出来るものが望ましいです．　

Solution: Implement password resetting function.
E-mail authentication and password change function can be re-used here. maybe.

If you have a time, also implement download history table for analyzing data.

In profile page (/profile ), Editing own profile should be enabled.
react-hook-form will be a choice of way of implementation.

• header's (dev) should be omitted.
• Write confirmation mail sending message when sign up was completed.
• backend authentication functions should be refactoring.
• activation_status item should be displayed in admin page and profile page.
• class_year registration should be constrained with databse information.
• signup function correctly works?
• download can be correctly done?
• File upload functions.
• authentication error handle.
• List use cases and validate its use.
• decide migration steps. how? ask part of people to register again?
• backend authentication validation.
• Omit backend test routes.

col--sm-4 or col--sm8 etc.. are not applied to the design.
Maybe mixin.sass are problematic.

As I edited clients services, I had to specify API_URL to access to backend.
However, when I deploy this code set, I should rewrite these parts.
Is there any way to change All the URL part? config setting or environmnet variables may be the solution.

If a user logs in, let user edit their profile information, especially password information.
Handle name and email should not be changed from this.

The way of passing state should be considered.

Backend side of user verification system should be implemented .
The problem is that if user make mistakes, and re-register, then same handlename and email can not be accepted in the current system. Fix it.
Also, automatic deletion of activation status or something is what i want to more.
ActivationToken should have the expire date. And if expired it should be not accepted any more. How ?

Expeired date for accessToken is desired to be added.
Now, if record accessToken and user is not try to login, using that token to access to server can be achivable.

If we can write services with setState, this is breakthrough!!
We can reduce much of the code volumes.

How to link the domain name to ip address?
I want to know the way with nginx or VPS.

The following tasks are remained in signup page .

• date validation. If date is not valid, return error.
• error popup problem. The way of error popup is not good.
• default option for date and 期, and its validation.
• reenteredPassword validation. Check same password is inputted.
• After successfuly sign up, back to login page.
• test framwork. Add sample user from signup page and login. Then delete the user in the end.

• Q1. ドメインは元のものを再利用するのですか？
  Ans. いいえ，新しく取得することにします．旧versionへのリンクを貼って遷移出来るようにしたいからです．
• Q2. DBは元のものを取り込むのですか？
  Ans. はい，取り込みます．データベースの構造を同じにしてしまえば，そのまんま流用することが出来ます．ちなみにDBはsqliteです．
• Q3. gmailアカウントは新規のものを取得しますか？
  Ans. はい，取得します．ただ，gmailが適切かどうかは微妙です．複数人で共有出来るものが望ましいです．　

After authentication system was implemented, it is troublesome process to develop each part.
Therefore I here write the progression status of authentication system.

• Admin authentication for frontend. All admin page can not be accessed without admin true status.
• Admin authentication for backend. Admin related controllers check admin status.
• User authentication for frontend. study, profile, logout.
• User authentication for frontend. navigation bar.
• User authentication for backend.

User authentication system should be implemented after setting up class semester specific view and file uploading and downloading functions.

After implementing user authentication system, you should switch temporal access and long accsess using localStorage and sessionStrorage.

This issue contains the packages or tools information for developing hokui_net_ver2.
Note : This documentation will be moved to README.md content.

Web application

Frontend

Backend

Other tools

Figma for hokui_net_ver2 can be viewed from
https://www.figma.com/file/ZqXn3uGx8qzqHhWiGZfZH4/hokui_net_2?node-id=0%3A1
If you want to edit this, please ask me. I will invite you.

Because of ambiguity of which version can Xserver can run,
check the version of nodejs which can be run in Xserver.

Also, try to use foreever package in order to daemonize the nodejs.
We can directly run the nodejs if daemonize the nodejs? or we have to set the port number settings or reverse proxy?

The way of center aligned are needed.

Sep 10 becomes Sep 9. Displaying problem or datetime setting problem .

Backend function of duplication function should be implemented.
errors are handled by msg data.

When signup and activation is done, send email to admin and enables admins to check the users.

Authentication error pages are needed.
Also checkout error code in html settings for authentication and data not found error should be examined.

May be col--sm around settings were problematic.

secretKey for jwt will be replaced with environmental vairable.
secretKey is defined in index.ts now.

As title says.
When applying _normalize.sass file, area disappears.

It is very trouble some process to check the content of sqlite.
Therefore, implement the page of looking at the contents of sqlite.
These pages will be viewed by admin users.

Because the architecture of the production will not be understood without screen transition diagram,
this task is high priority.

The behavior as the title says is not implemented.
It's also with SASS interaction maybe.

Validation should be required for troublesome process.

Email functions should be implemented.
We should implment email functions for the timings of signup and approval by admin.
Also we should take email address for this site. That may be [email protected].

Header font is mojibake, can not read in build version.

原因の該当箇所はこの辺り，
https://github.com/toshiakiasakura/hokui_net_ver2/blob/cce3d39108b607419e7e8ddf29880f32e2afabb8/client/src/components/login.component.tsx#L68-L75

sassとの設定に齟齬があると思われる．

Create ER diagram with drawio.
Reference codes are in db directory of original hokui.net source code.
This db is written by ruby.

If we do not add option of {nullable: true} in typeORM, it causes Connection error when createConnection function is activated.
The cause is unknown.

• サーバ作成直後に設定しておくべき初期セキュリティ設定
  https://manual.sakura.ad.jp/vps/support/security/firstsecurity.html

• SiteGuard Server Edition (WAF)
  https://manual.sakura.ad.jp/cloud/server/os-packages/siteguard-firewall.html